Comments (2)
Just a note to those who are reading this and wondering what to do about the time zone. This can be set in DailyPartitionsDefinition. @garethbrickman thanks for the detailed explanation.
from dagster.
The reason you cannot specify both the cron_schedule/execution_timezone
parameters and the day_of_month/day_of_week/hour_of_day/minute_of_hour
parameters at the same time when creating a schedule from a partitioned job is due to the design of the Dagster scheduling system. The build_schedule_from_partitioned_job
function is designed to create a schedule that aligns with the partitioning of the job. This means that the schedule's frequency and timing should match the intervals defined by the job's partitions.
When you define a partitioned job, you are effectively setting up a structure for how the data should be processed over time. For example, if you have a job that processes data daily, you would set up daily partitions. The schedule for this job should then naturally run once per day to process each partition.
The day_of_month
, day_of_week
, hour_of_day
, and minute_of_hour
parameters are used to specify the exact time within the partition's interval when the job should run. These parameters are meant to provide a convenient way to set the schedule based on the partition's natural frequency without having to manually calculate the corresponding cron expression.
On the other hand, the cron_schedule parameter
allows you to specify a custom cron expression that defines the schedule's frequency and timing in a more granular and flexible way. The execution_timezone
parameter is used in conjunction with cron_schedule
to ensure that the schedule runs at the correct local time, taking into account time zone differences.
Allowing both sets of parameters to be specified would create ambiguity and potential conflicts in the scheduling logic. For instance, if you set a daily partition but then provide a cron expression that runs every hour, it would be unclear how the schedule should reconcile the hourly cron expression with the daily partitioning of the job.
To maintain clarity and prevent such conflicts, Dagster requires you to use either the partition-based parameters or the cron-based parameters , but not both. This ensures that the schedule is consistent with the partitioning of the job and that there is a single source of truth for when and how often the job should run.
from dagster.
Related Issues (20)
- Code version of dagster dbt assets do not respect code of dependent macros and ephemeral models
- Add `dagster-cloud` and `dagster-insights` to `dagster-feedstock` on conda-forge HOT 1
- Allow metadata specification when manually reporting materialization from the UI
- Problem finding datetime_ambiguous on EMR HOT 5
- Change tags on existing operations
- Display queue criteria on the run detail page
- Dagster Cloud UI not showing logs for job runs HOT 3
- "ContextVar was created in a different Context" error from an async asset after successful materialization HOT 1
- dbt row count breaks on identifier which need quoting
- mlflow integration causes 429 error responses from Databricks when running multiple parallel jobs/ops HOT 2
- Asset daemon breaks when downgrading to 1.7.7 HOT 2
- dbt Freshness Check Fails w/ KeyError Due to "Missing" Metadata HOT 4
- run_status_sensor suddenly starts failing with `Expected non_None value`, possibly caused by ephemeral asset jobs HOT 2
- Monitoring ephemeral runs
- Race condition DuckDB in Dagster Essentials HOT 3
- Support generic type hints
- Asset Versioning with partitioned assets does not detect out-of-sync assets after incrementing code_version HOT 11
- Regression (v1.7.8) - Increased Time Required to start a dbt Project HOT 8
- Pull dagster-databricks Pipes into it's own library to remove dependency on Spark
- [UI] Comma after surname included in catalog greeting
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dagster.