feat: add analytics bucket sharding #796
Merged
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?
Feature
What is the current behavior?
Analytics buckets currently use a single undeline catalogue to store tables and namespaces.
Sometimes, Iceberg catalogues have limitations in the maximum number of iceberg tables they can accommodate.
What is the new behavior?
We implement sharding for analytics buckets, meaning that we can shard iceberg tables across multiple catalogues and being able to multiply the number of available tables that we can create and offer. Thus, it becomes a federated catalogue.
Additional context
sharding is optional, but needed when offering analytics buckets as multi-tenant service