You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dagster._core.errors.DagsterInvalidConfigError: Error in config for job continent_job
Error 1: Missing required config entry "ops" at the root. Sample config for missing entry: {'ops': {'continent_op': {'config': {'continent_name': '...'}}}}
I'm using latest version as of today, 1.6.1.
Additional information
I will try to
bissect to see if it's a "regression" (or documentation lacking update)
understand what is wrong with the code and propose doc update
Note that I do not know Dagster code though.
(not relevant for the issue - but why it's important to me!) I'm experimenting with Dagster and I have to prove feasibility for static partitioned jobs and dynamic outs before adoption. The full pipeline is 1) a partitioned asset (from pyarrow dataset based on hive partitioning) and 2 job/sequence of ops for chunking an parallel processing (but with this partition context)
Thanks!
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
The text was updated successfully, but these errors were encountered:
I've trie with multiple version, down to the latest 1.4, with the same result.
Note that it's not related to a missing configuration for execution. The code fails at the job definition (execution of @job decorator and subsequent validation)
What's the issue or suggestion?
Code sample in the section https://docs.dagster.io/concepts/partitions-schedules-sensors/partitioning-ops#defining-jobs-with-static-partitions is not working. Configuration is not propagated to the op, leading to this error (I've just copy-pasted the code and run it)
I'm using latest version as of today, 1.6.1.
Additional information
I will try to
Note that I do not know Dagster code though.
(not relevant for the issue - but why it's important to me!) I'm experimenting with Dagster and I have to prove feasibility for static partitioned jobs and dynamic outs before adoption. The full pipeline is 1) a partitioned asset (from pyarrow dataset based on hive partitioning) and 2 job/sequence of ops for chunking an parallel processing (but with this partition context)
Thanks!
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
The text was updated successfully, but these errors were encountered: