diff --git a/docs/docs-beta/docs/dagster-plus/features/catalog-views.md b/docs/docs-beta/docs/dagster-plus/features/catalog-views.md index ed9b2e452653b..750ee2781e7d8 100644 --- a/docs/docs-beta/docs/dagster-plus/features/catalog-views.md +++ b/docs/docs-beta/docs/dagster-plus/features/catalog-views.md @@ -17,7 +17,7 @@ In this guide, you'll learn how to create, access, and share catalog views with Prerequisites - **Organization Admin**, **Admin**, or **Editor** permissions on Dagster+ -- Familiarity with [Assets](/guides/build/create-asset-pipelines/assets-concepts/index.mdx and [Asset metadata](/guides/build/create-a-pipeline/metadata) +- Familiarity with [Assets](/guides/build/create-asset-pipelines/assets-concepts/index.mdx and [Asset metadata](/guides/build/create-asset-pipelines/metadata) diff --git a/docs/docs-beta/docs/dagster-plus/features/insights/asset-metadata.md b/docs/docs-beta/docs/dagster-plus/features/insights/asset-metadata.md index ba05db163f29d..e0aecebc1bef4 100644 --- a/docs/docs-beta/docs/dagster-plus/features/insights/asset-metadata.md +++ b/docs/docs-beta/docs/dagster-plus/features/insights/asset-metadata.md @@ -21,7 +21,7 @@ You'll need one or more assets that emit the same metadata key at run time. Insi are most valuable when you have multiple assets that emit the same kind of metadata, such as such as the number of rows processed or the size of a file uploaded to object storage. -Follow [the metadata guide](/guides/build/create-a-pipeline/metadata#runtime-metadata) to add numeric metadata +Follow [the metadata guide](/guides/build/create-asset-pipelines/metadata#runtime-metadata) to add numeric metadata to your asset materializations. ## Step 2: Enable viewing your metadata in Dagster+ Insights diff --git a/docs/docs-beta/docs/getting-started/installation.md b/docs/docs-beta/docs/getting-started/installation.md index ee3e627da1f0b..80b27bcbc49dd 100644 --- a/docs/docs-beta/docs/getting-started/installation.md +++ b/docs/docs-beta/docs/getting-started/installation.md @@ -70,4 +70,4 @@ If you encounter any issues during the installation process: ## Next steps - Get up and running with your first Dagster project in the [Quickstart](/getting-started/quickstart) -- Learn to [create data assets in Dagster](/guides/build/create-a-pipeline/data-assets) +- Learn to [create data assets in Dagster](/guides/build/create-asset-pipelines/data-assets) diff --git a/docs/docs-beta/docs/guides/automate/schedules.md b/docs/docs-beta/docs/guides/automate/schedules.md index 6fef3202822c4..b09dd49125b42 100644 --- a/docs/docs-beta/docs/guides/automate/schedules.md +++ b/docs/docs-beta/docs/guides/automate/schedules.md @@ -41,7 +41,7 @@ If using partitions and jobs, you can create a schedule using the partition with -If you have a [partitioned asset](/guides/build/create-a-pipeline/partitioning) and job: +If you have a [partitioned asset](/guides/build/create-asset-pipelines/partitioning) and job: diff --git a/docs/docs-beta/docs/guides/build/connect-to-external-systems/databases.md b/docs/docs-beta/docs/guides/build/connect-to-external-systems/databases.md index 92ebba3f9d033..3ec3d85a520e0 100644 --- a/docs/docs-beta/docs/guides/build/connect-to-external-systems/databases.md +++ b/docs/docs-beta/docs/guides/build/connect-to-external-systems/databases.md @@ -12,7 +12,7 @@ This guide demonstrates how to standardize database connections and customize th To follow the steps in this guide, you'll need: -- Familiarity with [Assets](/guides/build/create-a-pipeline/data-assets) +- Familiarity with [Assets](/guides/build/create-asset-pipelines/data-assets) To run the examples in this guide, you'll need: diff --git a/docs/docs-beta/docs/guides/build/create-asset-pipelines/assets-concepts/configuring-assets.md b/docs/docs-beta/docs/guides/build/create-asset-pipelines/assets-concepts/configuring-assets.md index c6273a3486008..47d3d023cc73b 100644 --- a/docs/docs-beta/docs/guides/build/create-asset-pipelines/assets-concepts/configuring-assets.md +++ b/docs/docs-beta/docs/guides/build/create-asset-pipelines/assets-concepts/configuring-assets.md @@ -13,7 +13,7 @@ You'll often want to be able to adjust parameters when materializing assets, whi To follow the steps in this guide, you'll need familiarity with: -- [Assets](/guides/build/create-a-pipeline/data-assets) +- [Assets](/guides/build/create-asset-pipelines/data-assets) - [Pydantic](https://docs.pydantic.dev/latest/) diff --git a/docs/docs-beta/docs/guides/build/create-asset-pipelines/data-assets.md b/docs/docs-beta/docs/guides/build/create-asset-pipelines/data-assets.md index 069564a11eac0..f587aff932527 100644 --- a/docs/docs-beta/docs/guides/build/create-asset-pipelines/data-assets.md +++ b/docs/docs-beta/docs/guides/build/create-asset-pipelines/data-assets.md @@ -72,5 +72,5 @@ flowchart LR ## Next steps - Learn to create [dependencies between assets](/guides/build/create-asset-pipelines/assets-concepts/asset-dependencies) -- Enrich Dagster's built-in data catalog with [asset metadata](/guides/build/create-a-pipeline/metadata) +- Enrich Dagster's built-in data catalog with [asset metadata](/guides/build/create-asset-pipelines/metadata) - Learn to use a [factory pattern](/guides/build/configure/asset-factories) to create multiple, similar assets diff --git a/docs/docs-beta/docs/guides/build/create-asset-pipelines/external-assets.md b/docs/docs-beta/docs/guides/build/create-asset-pipelines/external-assets.md index 482539981cc84..f958e17ca4532 100644 --- a/docs/docs-beta/docs/guides/build/create-asset-pipelines/external-assets.md +++ b/docs/docs-beta/docs/guides/build/create-asset-pipelines/external-assets.md @@ -21,7 +21,7 @@ For example, external assets could be: To follow the steps in this guide, you'll need: -- Familiarity with [Assets](/guides/build/create-a-pipeline/data-assets) +- Familiarity with [Assets](/guides/build/create-asset-pipelines/data-assets) - Familiarity with [Sensors](/guides/automate/sensors) diff --git a/docs/docs-beta/docs/guides/build/create-asset-pipelines/index.md b/docs/docs-beta/docs/guides/build/create-asset-pipelines/index.md index 41465b09cc6b6..4f14323e37cb0 100644 --- a/docs/docs-beta/docs/guides/build/create-asset-pipelines/index.md +++ b/docs/docs-beta/docs/guides/build/create-asset-pipelines/index.md @@ -46,10 +46,10 @@ Most Dagster pipelines follow these steps: To start building your Dagster pipeline, dive into the following guides: -- [Define data assets](/guides/build/create-a-pipeline/data-assets) +- [Define data assets](/guides/build/create-asset-pipelines/data-assets) - [Create dependencies between assets](/guides/build/create-asset-pipelines/assets-concepts/asset-dependencies) -- [Enrich assets with metadata](/guides/build/create-a-pipeline/metadata) -- [Partition assets](/guides/build/create-a-pipeline/partitioning) -- [Represent external data sources](/guides/build/create-a-pipeline/external-assets) +- [Enrich assets with metadata](/guides/build/create-asset-pipelines/metadata) +- [Partition assets](/guides/build/create-asset-pipelines/partitioning) +- [Represent external data sources](/guides/build/create-asset-pipelines/external-assets) By following these guides, you'll learn how to create powerful, maintainable data pipelines using Dagster's asset-based approach. diff --git a/docs/docs-beta/docs/guides/build/create-asset-pipelines/metadata.md b/docs/docs-beta/docs/guides/build/create-asset-pipelines/metadata.md index a271bb38f6335..ea82cb5cdc16d 100644 --- a/docs/docs-beta/docs/guides/build/create-asset-pipelines/metadata.md +++ b/docs/docs-beta/docs/guides/build/create-asset-pipelines/metadata.md @@ -19,7 +19,7 @@ Using metadata in Dagster, you can: To follow the steps in this guide, you'll need: -- Familiarity with [Assets](/guides/build/create-a-pipeline/data-assets) +- Familiarity with [Assets](/guides/build/create-asset-pipelines/data-assets) ## Adding owners to assets \{#owners} diff --git a/docs/docs-beta/docs/guides/build/create-asset-pipelines/partition-dependencies.md b/docs/docs-beta/docs/guides/build/create-asset-pipelines/partition-dependencies.md index d6ee59ba03478..14be62d3eb393 100644 --- a/docs/docs-beta/docs/guides/build/create-asset-pipelines/partition-dependencies.md +++ b/docs/docs-beta/docs/guides/build/create-asset-pipelines/partition-dependencies.md @@ -19,8 +19,8 @@ Partitioned assets in Dagster can have dependencies on other partitioned assets, To follow the steps in this guide, you'll need: -- Familiarity with [Assets](/guides/build/create-a-pipeline/data-assets) -- Familiarity with [Partitions](/guides/build/create-a-pipeline/partitioning) +- Familiarity with [Assets](/guides/build/create-asset-pipelines/data-assets) +- Familiarity with [Partitions](/guides/build/create-asset-pipelines/partitioning) diff --git a/docs/docs-beta/docs/guides/build/create-asset-pipelines/partitioning.md b/docs/docs-beta/docs/guides/build/create-asset-pipelines/partitioning.md index e82e16a28c601..b7af703bf186f 100644 --- a/docs/docs-beta/docs/guides/build/create-asset-pipelines/partitioning.md +++ b/docs/docs-beta/docs/guides/build/create-asset-pipelines/partitioning.md @@ -19,7 +19,7 @@ There are several ways to partition your data in Dagster: To follow the steps in this guide, you'll need: -- Familiarity with [Assets](/guides/build/create-a-pipeline/data-assets) +- Familiarity with [Assets](/guides/build/create-asset-pipelines/data-assets) diff --git a/docs/docs-beta/docs/guides/test/asset-checks.md b/docs/docs-beta/docs/guides/test/asset-checks.md index 8d457f4e45203..3372c80ecd817 100644 --- a/docs/docs-beta/docs/guides/test/asset-checks.md +++ b/docs/docs-beta/docs/guides/test/asset-checks.md @@ -40,7 +40,7 @@ A asset check is defined using the `@asset_check` decorator. The following example defines an asset check on an asset that fails if the `order_id` column of the asset contains a null value. The asset check will run after the asset has been materialized. - + ## Defining multiple asset checks \{#multiple-checks} @@ -53,13 +53,13 @@ The following example defines two asset checks using the `@multi_asset_check` de In this example, both asset checks will run in a single operation after the asset has been materialized. - + ## Programmatically generating asset checks \{#factory-pattern} Defining multiple checks can also be done using a factory pattern. The example below defines the same two asset checks as in the previous example, but this time using a factory pattern and the `@multi_asset_check` decorator. - + ## Blocking downstream materialization @@ -67,7 +67,7 @@ By default, if a parent's asset check fails during a run, the run will continue In the example bellow, if the `orders_id_has_no_nulls` check fails, the downstream `augmented_orders` asset won't be materialized. - + ## Scheduling and monitoring asset checks @@ -75,7 +75,7 @@ In some cases, running asset checks separately from the job materializing the as In the example below, two jobs are defined: one for the asset and another for the asset check. Schedules are defined to materialize the asset and execute the asset check independently. A sensor is defined to send an email alert when the asset check job fails. - + ## Next steps diff --git a/docs/docs-beta/docs/guides/test/data-freshness-testing.md b/docs/docs-beta/docs/guides/test/data-freshness-testing.md index a738941c2d8f5..d1d75d1ac3307 100644 --- a/docs/docs-beta/docs/guides/test/data-freshness-testing.md +++ b/docs/docs-beta/docs/guides/test/data-freshness-testing.md @@ -18,8 +18,8 @@ Freshness checks can also communicate SLAs for their data freshness. For example To follow the steps in this guide, you'll need familiarity with: -- [Assets](/guides/build/create-a-pipeline/data-assets) -- [External assets](/guides/build/create-a-pipeline/external-assets) +- [Assets](/guides/build/create-asset-pipelines/data-assets) +- [External assets](/guides/build/create-asset-pipelines/external-assets) - [Asset checks](/guides/test/asset-checks) @@ -45,7 +45,7 @@ The example below defines a freshness check on an asset that fails if the asset' ## External asset freshness \{#external-assets} -[External assets](/guides/build/create-a-pipeline/external-assets) are assets orchestrated by systems other than Dagster. +[External assets](/guides/build/create-asset-pipelines/external-assets) are assets orchestrated by systems other than Dagster. To run freshness checks on external assets, the checks need to know when the external assets were last updated. Emitting these update timestamps as values for the `dagster/last_updated_timestamp` observation metadata key allows Dagster to calculate whether the asset is overdue.