Skip to content
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

[FLINK] Change EventType from OTHER to RUNNING for running jobs #985

Merged
merged 2 commits into from
Aug 4, 2022

Conversation

mzareba382
Copy link
Contributor

@mzareba382 mzareba382 commented Aug 3, 2022

Problem

Within Flink integration, running jobs are sending events of type 'OTHER'. We should have an EventType with a name that clearly suggests that the event is currently running.

Solution

This change makes use of newly introduced 'RUNNING' EventType, which is a part of OpenLineage specification now and changes events from running Flink job to be of this type.

Related to: #972
Closes: #946

  • Your change modifies the core OpenLineage model
  • Your change modifies one or more OpenLineage facets

Checklist

  • You've signed-off your work
  • Your pull request title follows our guidelines
  • Your changes are accompanied by tests (if relevant)
  • Your change contains a small diff and is self-contained
  • You've updated any relevant documentation (if relevant)
  • You've updated the CHANGELOG.md with details about your change under the "Unreleased" section (if relevant, depending on the change, this may not be necessary)
  • You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
  • You've added a header to source files (if relevant)

Signed-off-by: mzareba <mzareba382@gmail.com>
Signed-off-by: mzareba <mzareba382@gmail.com>
@mzareba382 mzareba382 merged commit f392ba1 into main Aug 4, 2022
@mzareba382 mzareba382 deleted the flink/introduce-running-eventtype branch August 4, 2022 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use 'running' state instead of other
2 participants