Skip to content

Add Java SDK lineage IPC channel for OpenLineage #67111#67974

Open
haseebmalik18 wants to merge 1 commit into
apache:mainfrom
haseebmalik18:java-sdk-openlineage-lineage-ipc-channel
Open

Add Java SDK lineage IPC channel for OpenLineage #67111#67974
haseebmalik18 wants to merge 1 commit into
apache:mainfrom
haseebmalik18:java-sdk-openlineage-lineage-ipc-channel

Conversation

@haseebmalik18
Copy link
Copy Markdown
Contributor

Reserves the IPC channel and Java SDK API so JVM tasks can ship an opt-in lineage payload back to Python listeners.

The supervisor adds an optional lineage field on SucceedTask and TaskState, gated by a Cadwyn version change so the wire stays compatible with older clients. BaseCoordinator.on_lineage_received re-emits the payload through the listener manager as on_lang_task_lineage_received, and the Python coordinator path leaves the lineage_handler unwired so existing tasks pay nothing.

On the Java side, Context.setLineage and Context.putLineage give users an opt-in builder. Tasks that never call them produce the same wire bytes as before, which the existing byte-for-byte CommTest assertion still proves.

The OpenLineage provider listener does not yet consume on_lang_task_lineage_received.

closes: #67111

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.

Java-SDK OpenLineage support (lineage callback from Java task to Python supervisor)

1 participant