tests: Add OpenLineage to system tests in Google provider #46244
Conversation
This file contains 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
boring-cyborg
bot
added
area:providers
provider:google
kacpermuda
force-pushed
the
feat-ol-add-google-system-tests
branch
from
8ea0fd4 to
1cd354c
Compare
Signed-off-by: Kacper Muda <[email protected]>
kacpermuda
force-pushed
the
feat-ol-add-google-system-tests
branch
from
1cd354c to
b583752
Compare
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.
This PR adds checking OpenLineage events produced by selected Google Provider operators when running system checks. This is an addition to unit tests already checking OpenLineage for specific operators.
Thanks to VariableTransport introduced in #43643, we can easily check if OpenLineage events produced by any operator match the expected values. The logic is simple, for each system tests: adding the OpenLineageTestOperator to the DAG and providing it with json file with what we expect to be in the events. Whenever a system test is run, we will verify OpenLineage events emitted.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.