Repository navigation
feat(cli): emit lineage for assertions and property graphs - #2368
Merged
Merged
Conversation
…actionType with Backend Every action that runs a BigQuery job now emits lineage events. This covers tables, operations, assertions and property graphs. Declarations are still skipped. The gcp_bq_pipelines_job.actionType attribute now uses the same values as Dataform in Google Cloud: TABLE, OPERATIONS, ASSERTION and PROPERTY_GRAPH. For assertions the externalQuery facet references the CREATE VIEW job that writes the assertion view instead of the row count check query.
apilaskowski
approved these changes
Oct 13, 2026
apilaskowski
left a comment
apilaskowski
left a comment
Collaborator
There was a problem hiding this comment.
LGTM assuming review comments are resolved
Collaborator
Author
|
All the comments will be addressed in the follow up PR - #2373 |
rafal-hawrylak
added a commit
that referenced
this pull request
Oct 14, 2026
Follow-up to #2368: - Switch LINEAGE_ACTION_TYPES to ReadonlyMap and simplify isLineageEligibleAction - Replace internal doc reference in action_type.ts with inline Cloud Dataform enum values - Throw in LineagePayloadBuilder.build when called with an unsupported action type and test that LineageEmitter catches build errors - Clarify extractTargetWritingBqJobId docstring with Runner.executeAction and ExecutionSql.publishTasks references - Add end-to-end Runner test coverage for assertion externalQuery job ID selection - Clarify in cli/README.md that assertion dependencies and property graph ref dependencies are reported as inputs
rafal-hawrylak
added a commit
that referenced
this pull request
Oct 14, 2026
Follow-up to #2368: - Switch LINEAGE_ACTION_TYPES to ReadonlyMap and simplify isLineageEligibleAction - Replace internal doc reference in action_type.ts with inline Cloud Dataform enum values - Throw in LineagePayloadBuilder.build when called with an unsupported action type and test that LineageEmitter catches build errors - Clarify extractTargetWritingBqJobId docstring with Runner.executeAction and ExecutionSql.publishTasks references - Add end-to-end Runner test coverage for assertion externalQuery job ID selection - Clarify in cli/README.md that assertion dependencies and property graph ref dependencies are reported as inputs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
feat(cli): emit lineage for assertions and property graphs and align actionType with Backend
Every action that runs a BigQuery job now emits lineage events. This covers tables, operations, assertions and property graphs. Declarations are still skipped.
The gcp_bq_pipelines_job.actionType attribute now uses the same uppercase enum values as Dataform in Google Cloud: TABLE, OPERATIONS, ASSERTION and PROPERTY_GRAPH (replacing the previous lowercase table and operation values to match what Knowledge Catalog Lineage expects).
For assertions the externalQuery facet references the CREATE VIEW job that writes the assertion view instead of the row count check query, and the assertion's dependencies are reported as inputs. For property graphs the inputs are populated from dependencyTargets.