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

#sdy dynamically choose which custom_partitioning API to use based on the current #25834

Merged
merged 1 commit into from
Jan 14, 2025

Conversation

copybara-service[bot]
Copy link

#sdy dynamically choose which custom_partitioning API to use based on the current
value of the use_shardy_partitioner feature flag.

Before the way the API works depends on the value of the flag when the partitioning is defined. But we should allow this to be dynamically swapped in and out when the function is actually called. This change allows for that.

…on the current

value of the `use_shardy_partitioner` feature flag.

Before the way the API works depends on the value of the flag when the partitioning is defined. But we should allow this to be dynamically swapped in and out when the function is actually called. This change allows for that.

PiperOrigin-RevId: 715293018
@copybara-service copybara-service bot merged commit 74e912c into main Jan 14, 2025
1 of 2 checks passed
@copybara-service copybara-service bot deleted the test_714054637 branch January 14, 2025 10:12
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.

1 participant