-
Notifications
You must be signed in to change notification settings - Fork 3k
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
fix(ingest): fix reporting for missing secure view lineage #12430
fix(ingest): fix reporting for missing secure view lineage #12430
Conversation
Secure Views in databases created from Snowflake Shares will always be missing on view definitions and that need not be reported as warning. We would report such views as info in pipeline run.
Codecov ReportAll modified and coverable lines are covered by tests ✅
... and 9 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
except KeyError: | ||
# Received secure view definitions but the view is not present in results | ||
self.structured_reporter.info( | ||
"Secure view definition not found. Lineage will be missing for the view.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in general, let's always set both title and message for structured logs
otherwise the default title is "An unexpected issue occurred" which isn't great
metadata-ingestion/src/datahub/ingestion/source/snowflake/snowflake_schema_gen.py
Outdated
Show resolved
Hide resolved
…flake_schema_gen.py Co-authored-by: Harshal Sheth <[email protected]>
…roject#12430) Co-authored-by: Harshal Sheth <[email protected]>
Secure Views in databases created from Snowflake Shares will always be missing on view definitions and that need not be reported as warning. We would report such views as info in pipeline run.
Checklist