-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Added output_processor
parameter to BashProcessor
#40843
Merged
potiuk
merged 34 commits into
apache:main
from
dabla:feature/add-result-processor-bash-operator
Aug 5, 2024
Merged
Added output_processor
parameter to BashProcessor
#40843
potiuk
merged 34 commits into
apache:main
from
dabla:feature/add-result-processor-bash-operator
Aug 5, 2024
Conversation
This file contains 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
boring-cyborg
bot
added
area:core-operators
Operators, Sensors and hooks within Core Airflow
kind:documentation
labels
Jul 17, 2024
shahar1
reviewed
Jul 21, 2024
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.
Seems like a useful feature, got some few comments :)
Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
dabla
changed the title
Added result_processor parameter to BashProcessor
Added output_processor parameter to BashProcessor
Jul 29, 2024
shahar1
changed the title
Added output_processor parameter to BashProcessor
Added Aug 2, 2024
result_processor
parameter to BashProcessor
shahar1
changed the title
Added
Added Aug 2, 2024
result_processor
parameter to BashProcessor
output_processor
parameter to BashProcessor
shahar1
reviewed
Aug 4, 2024
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.
Almost there
Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
potiuk
approved these changes
Aug 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:core-operators
Operators, Sensors and hooks within Core Airflow
kind:documentation
type:improvement
Changelog: Improvements
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.
Added result_processor parameter to BashProcessor which allows you to specify a lambda function that processes the output of the bash script before it is pushed as an XCom. This feature is particularly useful for manipulating the script’s result directly within the BashOperator, without the need for additional operators or tasks.
If for example you have following bash script which uses the linux jq command to filter the required elements from a JSON-file, it is handy to have the XCom directly loaded as a JSON object in python instead of a string:
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.