Skip to content

Conversation

@bdsoha
Copy link
Contributor

@bdsoha bdsoha commented Oct 30, 2022

By adding Spark's appId to the xcom output, subsequent tasks can retrieve the application logs and resource usage.

Currently, the only available information is the batch_id which is Livy specific.

@bdsoha bdsoha marked this pull request as ready for review October 30, 2022 16:42
@bdsoha bdsoha force-pushed the feature/livy-xcom-app-id branch from b4f0c58 to 0faa595 Compare October 30, 2022 16:48
@bdsoha bdsoha force-pushed the feature/livy-xcom-app-id branch from 0faa595 to c1b7506 Compare October 30, 2022 16:49
@potiuk potiuk merged commit f75582a into apache:main Oct 31, 2022
@bdsoha bdsoha deleted the feature/livy-xcom-app-id branch October 31, 2022 05:55
pankajkoti added a commit to astronomer/airflow that referenced this pull request May 24, 2023
With the change in PR apache#27376, we started pushing the Spark appId
to XCOM when executing the Livy Operator in standard(non-defferable)
mode. This commit now pushed the appId to XCOM in deferrable mode
too to keep the expected outcome consistent for the operator so that
subsequent tasks can fetch and use the appId from XCOM.
jedcunningham pushed a commit that referenced this pull request May 25, 2023
With the change in PR #27376, we started pushing the Spark appId
to XCOM when executing the Livy Operator in standard(non-defferable)
mode. This commit now pushed the appId to XCOM in deferrable mode
too to keep the expected outcome consistent for the operator so that
subsequent tasks can fetch and use the appId from XCOM.
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.

2 participants