docs - dagster asset prefix key

Author: SumanMaharana

content/v1.11.x/connectors/pipeline/dagster/index.md

@@ -83,6 +83,28 @@ For a complete guide on managing secrets in hybrid setups, see the [Hybrid Inges
   - Give your API key a name and click on the "Create API Key" button.
   - Copy the generated API key to your clipboard and paste it in the field.
 
+### Strip Asset Key Prefix $(id="stripAssetKeyPrefix")
+
+Number of leading segments to remove from asset key paths before resolving to tables.
+
+**About Dagster Asset Keys:**
+
+Dagster asset keys are path-like identifiers represented as arrays of strings (e.g., `["project", "environment", "schema", "table"]`). When OpenMetadata ingests Dagster pipelines, it tries to match these asset keys to table entities using the standard format: `database.schema.table` or `schema.table`.
+
+**When to Use This Setting:**
+
+If your Dagster asset keys include additional prefix segments beyond the database/schema/table hierarchy, use this setting to strip those prefixes. For example:
+- Asset key: `["project", "environment", "schema", "table"]`
+- Set value to `2` to strip `project` and `environment`
+- Result: `schema.table` (matches OpenMetadata table entities)
+
+Common use cases include stripping:
+- Project/workspace identifiers
+- Environment names (dev/staging/prod)
+- Storage bucket/container prefixes
+
+Default value is `0` (no stripping).
+
 {% /extraContent %}
 
 {% partial file="/v1.11/connectors/test-connection.md" /%}
@@ -142,6 +164,53 @@ def customer_orders():
 | `["schema", "table"]` | Schema and table only |
 | `["table"]` | Table name only |
 
+**Using stripAssetKeyPrefix for Asset Keys with Prefixes**
+
+If your asset keys include additional prefix segments (e.g., project name, environment), use the `stripAssetKeyPrefix` configuration to remove them before matching to tables:
+
+**Example 1: Stripping Environment Prefix**
+
+```python
+# Your Dagster asset keys include environment prefix
+@asset(key=["prod", "analytics_db", "public", "customers"])
+def customers():
+    ...
+
+@asset(
+    key=["prod", "analytics_db", "public", "orders"],
+    deps=[customers]
+)
+def orders():
+    ...
+```
+
+**Configuration:**
+```yaml
+sourceConfig:
+  config:
+    stripAssetKeyPrefix: 1  # Remove the first segment ("prod")
+```
+
+**Result:** Asset keys become `["analytics_db", "public", "customers"]` and `["analytics_db", "public", "orders"]`, which match the table format `database.schema.table`.
+
+**Example 2: Stripping Multiple Prefixes**
+
+```python
+# Asset keys with project and environment prefixes
+@asset(key=["my_project", "staging", "warehouse", "raw", "users"])
+def users():
+    ...
+```
+
+**Configuration:**
+```yaml
+sourceConfig:
+  config:
+    stripAssetKeyPrefix: 2  # Remove first two segments ("my_project", "staging")
+```
+
+**Result:** Asset key becomes `["warehouse", "raw", "users"]`, matching `warehouse.raw.users` in OpenMetadata.
+
 **2. Assets Include Table Metadata in Materializations**
 
 If your assets don't use database-style keys, you can still get lineage by including table metadata when materializing:

content/v1.11.x/connectors/pipeline/dagster/yaml.md

@@ -75,9 +75,26 @@ This is a sample config for Dagster:
 **timeout** : Connection Time Limit Between OM and Dagster Graphql API in second
 {% /codeInfo %}
 
+{% codeInfo srNumber=4 %}
+
+**stripAssetKeyPrefix**: Number of leading segments to remove from asset key paths before resolving to tables.
+
+Dagster asset keys are path-like identifiers represented as arrays of strings (e.g., `["project", "environment", "schema", "table"]`). When OpenMetadata ingests Dagster pipelines, it tries to match these asset keys to table entities using the standard format: `database.schema.table` or `schema.table`.
+
+If your Dagster asset keys include additional prefix segments beyond the database/schema/table hierarchy, use this setting to strip those prefixes. For example:
+- Asset key: `["project", "environment", "schema", "table"]`
+- Set value to `2` to strip `project` and `environment`
+- Result: `schema.table` (matches OpenMetadata table entities)
+
+Common use cases include stripping project/workspace identifiers, environment names (dev/staging/prod), or storage bucket/container prefixes.
+
+Default value is `0` (no stripping).
+
+{% /codeInfo %}
+
 #### Source Configuration - Lineage
 
-{% codeInfo srNumber=4 %}
+{% codeInfo srNumber=5 %}
 
 **lineageInformation**: Configure lineage extraction settings.
 
@@ -120,6 +137,9 @@ source:
         # timeout: 1000
 ```
 ```yaml {% srNumber=4 %}
+        # stripAssetKeyPrefix: 0
+```
+```yaml {% srNumber=5 %}
   sourceConfig:
     config:
       type: PipelineMetadata

content/v1.11.x/main-concepts/metadata-standard/schemas/entity/services/connections/pipeline/dagsterConnection.md

@@ -13,6 +13,7 @@ slug: /main-concepts/metadata-standard/schemas/entity/services/connections/pipel
 - **`host`** *(string)*: URL to the Dagster instance.
 - **`token`** *(string)*: To Connect to Dagster Cloud.
 - **`timeout`** *(integer)*: Connection Time Limit Between OM and Dagster Graphql API in second. Default: `1000`.
+- **`stripAssetKeyPrefix`** *(integer)*: Number of leading segments to remove from asset key paths before resolving to tables. Dagster asset keys are path-like identifiers (e.g., `["project", "environment", "schema", "table"]`). Use this setting to strip prefix segments beyond the database/schema/table hierarchy. Default: `0`.
 - **`pipelineFilterPattern`**: Regex exclude pipelines. Refer to *../../../../type/filterPattern.json#/definitions/filterPattern*.
 - **`supportsMetadataExtraction`**: Refer to *../connectionBasicType.json#/definitions/supportsMetadataExtraction*.
 ## Definitions

content/v1.12.x-SNAPSHOT/connectors/pipeline/dagster/index.md

@@ -83,6 +83,28 @@ For a complete guide on managing secrets in hybrid setups, see the [Hybrid Inges
   - Give your API key a name and click on the "Create API Key" button.
   - Copy the generated API key to your clipboard and paste it in the field.
 
+### Strip Asset Key Prefix $(id="stripAssetKeyPrefix")
+
+Number of leading segments to remove from asset key paths before resolving to tables.
+
+**About Dagster Asset Keys:**
+
+Dagster asset keys are path-like identifiers represented as arrays of strings (e.g., `["project", "environment", "schema", "table"]`). When OpenMetadata ingests Dagster pipelines, it tries to match these asset keys to table entities using the standard format: `database.schema.table` or `schema.table`.
+
+**When to Use This Setting:**
+
+If your Dagster asset keys include additional prefix segments beyond the database/schema/table hierarchy, use this setting to strip those prefixes. For example:
+- Asset key: `["project", "environment", "schema", "table"]`
+- Set value to `2` to strip `project` and `environment`
+- Result: `schema.table` (matches OpenMetadata table entities)
+
+Common use cases include stripping:
+- Project/workspace identifiers
+- Environment names (dev/staging/prod)
+- Storage bucket/container prefixes
+
+Default value is `0` (no stripping).
+
 {% /extraContent %}
 
 {% partial file="/v1.12/connectors/test-connection.md" /%}
@@ -142,6 +164,53 @@ def customer_orders():
 | `["schema", "table"]` | Schema and table only |
 | `["table"]` | Table name only |
 
+**Using stripAssetKeyPrefix for Asset Keys with Prefixes**
+
+If your asset keys include additional prefix segments (e.g., project name, environment), use the `stripAssetKeyPrefix` configuration to remove them before matching to tables:
+
+**Example 1: Stripping Environment Prefix**
+
+```python
+# Your Dagster asset keys include environment prefix
+@asset(key=["prod", "analytics_db", "public", "customers"])
+def customers():
+    ...
+
+@asset(
+    key=["prod", "analytics_db", "public", "orders"],
+    deps=[customers]
+)
+def orders():
+    ...
+```
+
+**Configuration:**
+```yaml
+sourceConfig:
+  config:
+    stripAssetKeyPrefix: 1  # Remove the first segment ("prod")
+```
+
+**Result:** Asset keys become `["analytics_db", "public", "customers"]` and `["analytics_db", "public", "orders"]`, which match the table format `database.schema.table`.
+
+**Example 2: Stripping Multiple Prefixes**
+
+```python
+# Asset keys with project and environment prefixes
+@asset(key=["my_project", "staging", "warehouse", "raw", "users"])
+def users():
+    ...
+```
+
+**Configuration:**
+```yaml
+sourceConfig:
+  config:
+    stripAssetKeyPrefix: 2  # Remove first two segments ("my_project", "staging")
+```
+
+**Result:** Asset key becomes `["warehouse", "raw", "users"]`, matching `warehouse.raw.users` in OpenMetadata.
+
 **2. Assets Include Table Metadata in Materializations**
 
 If your assets don't use database-style keys, you can still get lineage by including table metadata when materializing:

content/v1.12.x-SNAPSHOT/connectors/pipeline/dagster/yaml.md

@@ -75,9 +75,26 @@ This is a sample config for Dagster:
 **timeout** : Connection Time Limit Between OM and Dagster Graphql API in second
 {% /codeInfo %}
 
+{% codeInfo srNumber=4 %}
+
+**stripAssetKeyPrefix**: Number of leading segments to remove from asset key paths before resolving to tables.
+
+Dagster asset keys are path-like identifiers represented as arrays of strings (e.g., `["project", "environment", "schema", "table"]`). When OpenMetadata ingests Dagster pipelines, it tries to match these asset keys to table entities using the standard format: `database.schema.table` or `schema.table`.
+
+If your Dagster asset keys include additional prefix segments beyond the database/schema/table hierarchy, use this setting to strip those prefixes. For example:
+- Asset key: `["project", "environment", "schema", "table"]`
+- Set value to `2` to strip `project` and `environment`
+- Result: `schema.table` (matches OpenMetadata table entities)
+
+Common use cases include stripping project/workspace identifiers, environment names (dev/staging/prod), or storage bucket/container prefixes.
+
+Default value is `0` (no stripping).
+
+{% /codeInfo %}
+
 #### Source Configuration - Lineage
 
-{% codeInfo srNumber=4 %}
+{% codeInfo srNumber=5 %}
 
 **lineageInformation**: Configure lineage extraction settings.
 
@@ -120,6 +137,9 @@ source:
         # timeout: 1000
 ```
 ```yaml {% srNumber=4 %}
+        # stripAssetKeyPrefix: 0
+```
+```yaml {% srNumber=5 %}
   sourceConfig:
     config:
       type: PipelineMetadata

content/v1.12.x-SNAPSHOT/main-concepts/metadata-standard/schemas/entity/services/connections/pipeline/dagsterConnection.md

@@ -13,6 +13,7 @@ slug: /main-concepts/metadata-standard/schemas/entity/services/connections/pipel
 - **`host`** *(string)*: URL to the Dagster instance.
 - **`token`** *(string)*: To Connect to Dagster Cloud.
 - **`timeout`** *(integer)*: Connection Time Limit Between OM and Dagster Graphql API in second. Default: `1000`.
+- **`stripAssetKeyPrefix`** *(integer)*: Number of leading segments to remove from asset key paths before resolving to tables. Dagster asset keys are path-like identifiers (e.g., `["project", "environment", "schema", "table"]`). Use this setting to strip prefix segments beyond the database/schema/table hierarchy. Default: `0`.
 - **`pipelineFilterPattern`**: Regex exclude pipelines. Refer to *../../../../type/filterPattern.json#/definitions/filterPattern*.
 - **`supportsMetadataExtraction`**: Refer to *../connectionBasicType.json#/definitions/supportsMetadataExtraction*.
 ## Definitions