-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Stored Procedures as another entity under Database Schema #12998
Comments
IngestionFor Snowflake:
For Redshift:
For BigQuery:
For Postgres: |
…3215) * Update mapping * Prep * prep * Prep query migration * Add query index deletion fix * Docs and Maven CI fix * Fix tests * Add service filter * Add query entity FQN col migration * Fix lint * supported serviceFQN in query api * Prep repo * Prep ES query search * Do not recompute lineage * Format * Fix test --------- Co-authored-by: Ashish Gupta <ashish@getcollate.io>
Hi, will we able to build pipelines and lineage based on stored procedures? We call procedures in MSSQL Jobs – usually 1 step = 1 procedure |
hi @asprdnv Stored Procedures are ingested under the Database Schema that they live in. Not sure if we'll have enough room to handle MSSQL for 1.2.0. If not, we'll add them in 1.2.1 |
Hi, how about Oracle Stored Procedure? Do you have any plan for it? |
Hi @pmbrull , Do you have any plan to implement Stored Procedure for Oracle? |
Hello @nqvuong1998 Yes, that's is on the roadmap and we plan to bring it in the upcoming release. |
@nqvuong1998 you can track the fix for the same from here: #14641 |
Is your feature request related to a problem? Please describe.
Stored Procedures important entity in a database, many users are expressed interest in capturing metadata about stored procedures and potentially lineage
Describe the solution you'd like
We will be adding Stored Procedure as another entity with a parent container as the Database Schema.
There will be APIs under /api/v1/storedProcedures to capture the metadata about Stored Procedures
Related issues
The text was updated successfully, but these errors were encountered: