bhavya2109sharma opened a new pull request, #69002:
URL: https://github.com/apache/airflow/pull/69002

   ## Description 
   
   - Add the ability for SageMakerProcessingOperator to read small JSON output 
files from S3 after a processing job completes and push their parsed contents 
to XCom. This lets downstream tasks (e.g. a SageMakerConditionOperator) consume 
metrics produced by Processing Job.
   
   - `output_files_to_xcom` (new kwarg on SageMakerProcessingOperator): a list 
of dicts describing which output files to read after the job finishes. Each 
entry has:
         - `output_name` -  matches an OutputName declared in 
ProcessingOutputConfig.Outputs (used to locate that output's S3 URI)
         - `file_name` — the JSON file your processing script wrote inside that 
output
         - `result_name` — the label for the parsed contents in the returned 
OutputFiles dict
   - Parsed files are returned under an OutputFiles key in the operator's XCom 
result (alongside the existing Processing job description).
   - Opt-in and backwards-compatible: when `output_files_to_xcom` is omitted, 
behavior is unchanged.
   - Intended for small JSON summaries (metrics, evaluation reports), not large 
datasets.
   
   ## Usage
   Read an evaluation metrics file and push it to XCom:
   
   ```
   preprocess = SageMakerProcessingOperator(
       task_id="evaluate",
       config={
           "ProcessingJobName": "evaluate-model",
           "ProcessingOutputConfig": {
               "Outputs": [
                   {
                       "OutputName": "evaluation",
                       "S3Output": {
                           "S3Uri": "s3://my-bucket/evaluation",
                           "LocalPath": "/opt/ml/processing/output/evaluation",
                           "S3UploadMode": "EndOfJob",
                       },
                   }
               ]
           },
           # ... AppSpecification, ProcessingInputs, ProcessingResources, 
RoleArn
       },
       output_files_to_xcom=[
           {"output_name": "evaluation", "file_name": "metrics.json", 
"result_name": "EvaluationReport"}
       ],
   )
   
   ```
   Downstream task reads the parsed metrics from XCom:
   
   ```
   check = SageMakerConditionOperator(
       task_id="check_accuracy",
       condition_type="GreaterThanOrEqualTo",
       left_value="{{ 
ti.xcom_pull(task_ids='evaluate')['OutputFiles']['EvaluationReport']['mse'] }}",
       right_value=8.0,
       if_task_ids=["register_model"],
       else_task_ids=["retrain"],
   )
   
   ```
   
   ## Testing 
   Unit tests
   ```
   breeze testing providers-tests --test-type "Providers[amazon]" -- 
providers/amazon/tests/unit/amazon/aws/operators/test_sagemaker_processing.py::TestSageMakerProcessingOperatorOutputFiles
 -xvs
   
   ```
   
   System tests
   ```
   breeze shell --forward-credentials --mount-sources all
   pytest providers/amazon/tests/system/amazon/aws/example_sagemaker.py 
--system -xvs 
   ```
    <!-- SPDX-License-Identifier: Apache-2.0
         https://www.apache.org/licenses/LICENSE-2.0 -->
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull 
request.
   Write a good git commit message following this guide: 
http://chris.beams.io/posts/git-commit/
   
   Please make sure that your code changes are covered with tests.
   And in case of new features or big changes remember to adjust the 
documentation.
   
   For user-facing UI changes, please attach before/after screenshots (or a 
short
   screen recording) so reviewers can assess the visual impact.
   
   Feel free to ping (in general) for the review if you do not see reaction for 
a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we 
sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [X] Yes Claude Opus 4.6
   
   <!--
   Generated-by: Opus 4.6 following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
 You can add this file in a follow-up commit after the PR is created so you 
know the PR number.
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to