-
Notifications
You must be signed in to change notification settings - Fork 293
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
NR-347971 | OpenLineage event consumer writer #1887
NR-347971 | OpenLineage event consumer writer #1887
Conversation
NR-347971 | Added filter condition on unique attribute
- updatedAt | ||
name: job.name | ||
encodeIdentifierInGUID: true | ||
conditions: |
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.
It looks like the conditions for this definition are the same ones than for OLIN_JOBS. The conditions should have some differentiation to avoid collisions
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.
I have added following condition to differentiate between events since the updatedAt
field should be present only in OLIN_JOB_VERSIONS
. Is this sufficient?
#OLIN_JOBS
- attribute: updatedAt
present: false
#OLIN_JOB_VERSIONS
- attribute: updatedAt
present: true
I have written similar conditions for OLIN_DATASETS
vs OLIN_DATASET_VERSIONS
To be merged after the freeze window |
This reverts commit 7c9f7fc.
This reverts commit 7c9f7fc. Co-authored-by: Adrian <[email protected]>
Relevant information
Added domain and entities for Data Pipeline Observability product
Checklist
identifier
will be unique and valid.