Skip to content

feature: support local sources for processing inputs - #6458

Open
gauravkriplani wants to merge 1 commit into
aws:masterfrom
gauravkriplani:fix/processing-input-local-source
Open

gauravkriplani wants to merge 1 commit into
aws:masterfrom
gauravkriplani:fix/processing-input-local-source

Conversation

@gauravkriplani

Copy link
Copy Markdown

Summary

  • support v2-compatible ProcessingInput(source=..., destination=...) construction in SDK v3
  • automatically stage local processing inputs through the existing S3 uploader
  • preserve service-level s3_input and dataset_definition construction
  • keep handwritten compatibility behavior separate from generated AWS service shapes

Problem

SDK v3 requires users to manually construct a nested ProcessingS3Input, even though the processor already knows how to upload non-S3 sources. This restores the convenient local-path workflow without modifying generated shape code.

Testing

  • pytest -q sagemaker-core/tests/unit/test_processing.py sagemaker-core/tests/unit/generated/test_shapes.py — 140 passed
  • verified local file upload destination and returned S3 URI propagation
  • verified both public import paths expose the compatibility constructor
  • black --check
  • git diff --check

Fixes #5672

This branch is waiting to be deployed

1 waiting deployment
manual-approval — 2f29d791 Waiting Oct 13, 2026 by gauravkriplani via wait-for-approval #1746
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support local source for sagemaker.core.shapes.ProcessingInput

1 participant