metadata range asset checks

[johannkm]

Add an experimental build_metadata_range_checks factory for asserting that a numeric metadata value is within a range.

@asset
def my_asset():
  return MaterializeResult(metadata={"my_metadata": 5})

checks = build_metadata_range_checks(
  assets=[my_asset], metadata_key="my_metadata", min_value=1, max_value=10
)

[johannkm]

• #21630 👈
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @johannkm and the rest of your teammates on Graphite

[github-actions[bot]]

Deploy preview for dagster-docs ready!

Preview available at https://dagster-docs-1d6bu7ab8-elementl.vercel.app https://johann-05-03-metadata-range-check.dagster.dagster-docs.io

Direct link to changed pages:

• https://dagster-docs-1d6bu7ab8-elementl.vercel.app https://johann-05-03-metadata-range-check.dagster.dagster-docs.io/concepts/dagster-pipes/databricks
• https://dagster-docs-1d6bu7ab8-elementl.vercel.app https://johann-05-03-metadata-range-check.dagster.dagster-docs.io/integrations/airbyte
• https://dagster-docs-1d6bu7ab8-elementl.vercel.app https://johann-05-03-metadata-range-check.dagster.dagster-docs.io/integrations/databricks

[sryza]

As I think about more places where these names will show up – e.g. a button in the UI next to a metadata value that allows creating a check from it –, I feel less convinced on "limit". "Limit" feels like it has the connotation of "rate limit" or "select * from x limit 5".

This leads me to lean more towards something like "bound" or "threshold". Maybe worth getting the opinions of the dev rel folks?

[johannkm]

updated to bounds