Skip to content
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

introduce flags for customizing standard providers using their own YA… #34158

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

zilin
Copy link

@zilin zilin commented Mar 4, 2025

Allow customization of standard providers via YAML files

This commit introduces two new command-line flags, --standard_io_yaml_file and --standard_providers_yaml_file, enabling users to customize the standard providers used when executing Apache Beam YAML pipelines.

  • --standard_io_yaml_file: Specifies a YAML file containing definitions for standard I/O providers, allowing users to override or extend the default I/O providers.
  • --standard_providers_yaml_file: Specifies a YAML file containing definitions for other standard providers (i.e., non-I/O providers), providing similar customization capabilities.

The standard_providers function in yaml_provider.py has been updated to load providers from these user-specified files if provided, falling back to the default standard providers if the flags are not used.

These changes provide greater flexibility and extensibility when defining and running Beam pipelines with YAML, allowing users to tailor the available transforms and I/O connectors to their specific needs.


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Copy link
Contributor

github-actions bot commented Mar 4, 2025

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

@zilin zilin force-pushed the master branch 5 times, most recently from 17d1473 to b35c571 Compare March 4, 2025 20:18
Copy link
Contributor

github-actions bot commented Mar 4, 2025

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @shunping for label python.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

@shunping
Copy link
Collaborator

shunping commented Mar 4, 2025

@derrickaw could you help to review this? Maybe you have more context on this PR.

@shunping shunping requested a review from derrickaw March 4, 2025 23:12
@derrickaw
Copy link
Collaborator

Hi @shunping, I don't have any context on this part, sorry.

@derrickaw derrickaw requested review from robertwb and removed request for derrickaw March 7, 2025 15:05
@robertwb
Copy link
Contributor

robertwb commented Mar 7, 2025

I have the context here, can be a reviewer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants