Add Spark's appId to xcom output#27376
Merged
potiuk merged 8 commits intoapache:mainfrom Oct 31, 2022
Merged
Conversation
b4f0c58 to
0faa595
Compare
0faa595 to
c1b7506
Compare
…into feature/livy-xcom-app-id
potiuk
approved these changes
Oct 31, 2022
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.
This file contains hidden or 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
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.
By adding Spark's
appIdto thexcomoutput, subsequent tasks can retrieve the application logs and resource usage.Currently, the only available information is the
batch_idwhich is Livy specific.