https://dagster.io/ logo
#ask-community
Title
# ask-community
n

Nathan Skone

05/01/2023, 4:34 PM
Reposting since this may have been lost over the weekend: Hello, we are migrating out Dagster jobs from the old
@repository
to the new
Definitions
style jobs. So far the migration is going great, but one thing we noticed is that the Launchpad no longer populates with config when shift-clicking the “Materialize all” button. Instead now we get an error:
Missing required config entries
and need to click the “Scaffold missing config” button. This feels like a step backwards in terms of our user experience. Is there a specific way that config needs to be provided to a Definition so that it will populate in the Launchpad? Note that the config is passed correctly when normally clicking the materialize button (not shift-clicking). We are on Dagster 1.2.7.
y

yuhan

05/01/2023, 4:54 PM
Hi Nathan, surfacing default config better is an area we’re focused on. What’s your before and after config specification like? (e.g. provided via job defs, set as default values in config in each op or asset, etc?)
n

Nathan Skone

05/01/2023, 4:56 PM
Before:
Copy code
job = build_assets_job(
    name=self.name,
    assets=self.assets,
    source_assets=self.assets,
    resource_defs=self.get_resource_defs(),
    tags=self.tags,
    config=self.get_config(),
    partitions_def=self.partitions_def,
)
@repository
def repo():
    return {"jobs": {"job_name: job}}
After:
Copy code
job = define_asset_job(
    name="job_name",
    config=configuration.load(),
    selection=[datadog_metrics_asset],
}
Definitions(
    assets=[datadog_metrics_asset],
    jobs=[job],
    schedules=[build_schedule_from_partitioned_job(job)],
    sensors=get_datadog_sensors(job),
)
@yuhan To summarize: Before we used
from dagster._core.definitions.assets_job import build_assets_job
and
@repository
After we are using
from dagster import define_asset_job
and
from dagster import Definitions
. In both cases the config is being passed into the
job
y

yuhan

05/01/2023, 10:37 PM
im trying to repro it on my end. here’s what i got:
Copy code
from dagster import define_asset_job, repository, asset, Definitions


@asset
def asset1():
    return 1


@asset(config_schema={"path": str})
def asset2(context, asset1):
    print(context.op_config["path"])
    return 2


my_job = define_asset_job(
    "boo", [asset1, asset2], config={"ops": {"asset2": {"config": {"path": "foo"}}}}
)
same asset and job code
before using repo:
Copy code
@repository
def repo():
    return [asset1, asset2, my_job]
after using Definitions:
Copy code
defs = Definitions(assets=[asset1, asset2], jobs=[my_job])
in both cases, i got the config that i specified on the
define_asset_job
on populates in the UI as below
curious if this is the same set up as yours, or did i miss anything?
n

Nathan Skone

05/01/2023, 11:00 PM
@yuhan That looks the same as mine, the only difference is that my job is a partitioned job. Maybe that is an edge case?
Also I am on version 1.2.7
y

yuhan

05/01/2023, 11:02 PM
hmm in your after block, i dont see a
partitions_def
arg to the
define_asset_job
. could that be the issue?
meanwhile let me try partitioned job
n

Nathan Skone

05/01/2023, 11:04 PM
I left the
@asset
code out of my block, and that is the only place we are using a
partitions_def
. Should a
partitions_def
be applied to the job or the definition as well?
maybe that is what I am missing… I am not setting
partitions_def
on the
define_asset_job
call?
Funny that the job still works great other than this one issue
I added
partitions_def
to the
define_asset_job
call and it did not have any apparent affect
y

yuhan

05/01/2023, 11:11 PM
mind sharing your asset code a bit? wanted to understand how the config and partition key are defined on assets
n

Nathan Skone

05/01/2023, 11:12 PM
Copy code
PARTITION_DEFINITION = HourlyPartitionsDefinition(
    start_date=datetime(2022, 12, 28), timezone="Etc/UTC"
)
@asset(
    name="datadog_metrics_asset",
    partitions_def=PARTITION_DEFINITION,
    required_resource_keys={"warehouse"},
    config_schema={
        "bucket": str,
        "redshift_role": str,
        "datadog_api_key": Any,
        "datadog_app_key": Any,
    },
    retry_policy=RetryPolicy(  # delay is in seconds
        max_retries=3, delay=10, backoff=Backoff.EXPONENTIAL
    ),
)
def datadog_metrics_asset(context) -> None:
    start, end = context.output_asset_partitions_time_window()
    <http://context.log.info|context.log.info>(
        f"We will be querying DataDog for metric points starting at {start} and ending at {end}"
    )
y

yuhan

05/01/2023, 11:12 PM
thanks! and the config is reported to be missing in the UI is these right?
Copy code
config_schema={
        "bucket": str,
        "redshift_role": str,
        "datadog_api_key": Any,
        "datadog_app_key": Any,
    },
n

Nathan Skone

05/01/2023, 11:14 PM
Correct.
y

yuhan

05/01/2023, 11:22 PM
interesting enough that even with repository, when i have this code:
Copy code
from dagster import (
    define_asset_job,
    repository,
    asset,
    HourlyPartitionsDefinition,
    Definitions,
)

hourly_partitions_def = HourlyPartitionsDefinition(start_date="2022-05-31-00:00")


@asset(partitions_def=hourly_partitions_def)
def asset1():
    return 1


@asset(partitions_def=hourly_partitions_def, config_schema={"path": str})
def asset2(context, asset1):
    print(context.op_config["path"])
    return 2


my_job = define_asset_job(
    "boo",
    [asset1, asset2],
    partitions_def=hourly_partitions_def,
    config={"ops": {"asset2": {"config": {"path": "foo"}}}},
)


@repository
def repo():
    return [asset1, asset2, my_job]
the UI prompts “missing config” and when i select the partition key, it ends up populating the full config. i believe this is an expected behavior as partition_key in an input to the config blob. in other words, for a partitioned job, when a partition key isn’t specified, dagster doesn’t know of the full config values, and therefore won’t populate the values.
n

Nathan Skone

05/01/2023, 11:23 PM
Ahhh…. thank you! So it was a user issue after all 🙂
I think the UI was a bit confusing in this case, the error message could have been easier to understand
But this does make sense
y

yuhan

05/01/2023, 11:24 PM
agreed. going to surface to our UI/UX team!
n

Nathan Skone

05/01/2023, 11:24 PM
Thank you again!
I appreciate the time and effort
🫡 1
4 Views