Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
-- Currently, OpenMetadata captures metadata and lineage for Snowflake tables, but it does not ingest metadata for Snowflake stages (internal or external). In Snowflake pipelines, it's common for data to be staged (via internal or named stages) before being loaded into a table using COPY INTO commands.
This leads to an incomplete lineage view in OpenMetadata, especially when trying to trace a data pipeline's origin (e.g., a file upload or intermediate processing result) through to the final table.
Describe the solution you'd like
A clear and concise description of what you want to happen.
- Ingest metadata for Snowflake stages (internal, external, and table stages if possible).
- Capture references to stage paths in COPY INTO operations.
- Represent stage entities in lineage diagrams to bridge gaps between pipelines and tables.
- Optionally, add config toggle for users who may not want to include stage-level metadata.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
-- Currently, OpenMetadata captures metadata and lineage for Snowflake tables, but it does not ingest metadata for Snowflake stages (internal or external). In Snowflake pipelines, it's common for data to be staged (via internal or named stages) before being loaded into a table using COPY INTO commands.
This leads to an incomplete lineage view in OpenMetadata, especially when trying to trace a data pipeline's origin (e.g., a file upload or intermediate processing result) through to the final table.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.