🌱 Update shard naming to allow for 1M+ shards #1170
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Integration tests success for 47db863221cdf16de4b07cc75696b42e5e57ad59 |
inferno-chromium
approved these changes
Oct 27, 2021
azeemshaikh38
force-pushed
the
azeems/shards
branch
from
47db863 to
d289567
Compare
Done |
|
Integration tests success for d2895679a831b18117dd817260beacf5246b76da |
oliverchang
approved these changes
Oct 27, 2021
|
Integration tests success for d6f78f37a8c1c2ea834c793d53ad5799ace1a12e |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Update shard naming convention to allow for >100k shards.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.