Idea: Shard by geolocation
Open
feature
- Dominant language
- C
- Stars
- 12.8k
- Forks
- 794
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 31
Description
### Goal
Being able to store all records related to users in one geolocation only on workers in that geolocation.
### Options
#### Create a distributed table for each geolocation
Need some way to wrap encapsulate the tables
#### Distribute a table by multiple columns
Elegant, but requires a lot of changes:
- the planner needs to detect a join on two columns
- range (geo_location) + hash (tenant) distribution would be nice
Contributor guide
Assessment
This issue has not been assessed yet.