Meituan-Dianping / Meituan-Dianping/DBProxy
支持多子表联合查询不？
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 2.3k
- Forks
- 554
- PR merge metrics
- No merged PRs in 30d
Description
有两张表A， B， 他们都是大数据表，将他们按各自的分表键分表之后变成了A_0, A_1, B_0， B_1.
select a.name, b.name as n2
from A a
INNER JOIN B b on a.xx= b.yyy
where a.shardingKey=xxx and b.shardingKey=yyy
最终不会生成分表 的join语句类似(e.g. select a.name, b.name as n2 from A_0 a inner join B_1 b on a.xx=b.yyy)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing how sharding keys are routed for joins, then reproduce the A/B query with the stated predicates and compare the generated SQL with the expected A_0/B_1 join. Done means the requested multi-sharded-table join is supported and covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100