Currently all shards are queried for every sharded table query. When the WHERE clause contains the shard key (e.g., WHERE user_id = 42), the distributed planner should route to only the relevant shard.
Requires:
- Analyze WHERE clause for shard key predicates
- Shard map with range/hash-based routing logic
- Only send queries to matching shards
Currently all shards are queried for every sharded table query. When the WHERE clause contains the shard key (e.g.,
WHERE user_id = 42), the distributed planner should route to only the relevant shard.Requires: