[DOP-26403] Set output type based on SQL query type #310
Conversation
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
dolfinus
force-pushed
the
feature/DOP-26403
branch
from
87b873e to
1bf3aa0
Compare
dolfinus
force-pushed
the
feature/DOP-26403
branch
from
1bf3aa0 to
e4d3bb6
Compare
dolfinus
force-pushed
the
feature/DOP-26403
branch
from
e4d3bb6 to
e220566
Compare
TiGrib
approved these changes
Sep 16, 2025
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.
Change Summary
Now
output.typecolumn is filled up based on SQL query type (INSERT,UPDATE, and so on). This is done because OpenLineageLifecycleStateChangefacet is limited to DDL operations (CREATE,ALTER,DROP,TRUNCATE), but OutputType is more broad concept.Related issue number
Checklist
docs/changelog/next_release/<pull request or issue id>.<change type>.rstfile added describing change(see CONTRIBUTING.rst for details.)