danihodovic opened a new pull request #9885: URL: https://github.com/apache/airflow/pull/9885
Use case 1: I want to use the SimpleHttpOperator to retrieve API data and pass it to another operator via xcom. The API I'm retrieving data from is returning JSON in megabytes. I don't want to save megabytes to the metadata database. Instead I want to filter and manipulate the response data to only contain the subset of data I'm interested in. Use case 2: I want to pass JSON parsed data (as a python dictionary) from the SimpleHttpOperator to other tasks instead of raw text. Use case 3: I'm not interested in the response HTTP body and instead want to retrieve HTTP headers or status codes and pass it to my downstream tasks. --- Make sure to mark the boxes below before creating PR: [x] - [ ] Description above provides context of the change - [ ] Unit tests coverage for changes (not needed for documentation changes) - [ ] Target Github ISSUE in description if exists - [ ] Commits follow "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)" - [ ] Relevant documentation is updated including usage instructions. - [ ] I will engage committers as explained in [Contribution Workflow Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example). --- In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md). Read the [Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines) for more information. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
