Uh oh!
There was an error while loading. Please reload this page.
feat: composite RANGE, semi-join prune, PG LIST/RANGE + 2PC demo - #62
Conversation
- Composite RANGE now routes and prunes on the first key component (LIST still rejects composites; HASH uses all parts). - Semi-join prune: when one side of a join is sharded and the other is not, the engine materializes the small side and pushes an IN-list onto the sharded probe side. - New demo scripts for PostgreSQL shards (16432/16433) exercising RANGE + LIST + cross-shard 2PC with DistributedTransactionManager in POSTGRESQL mode. - sqlengine now auto-selects PostgreSQL 2PC dialect when all backends are pgsql://. - Added planner and live-backend tests; full suite now 1344 passed. Stacked on PR #61.
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Uh oh!
There was an error while loading. Please reload this page.
Summary
RANGEnow routes and prunes on the first key component (LIST still rejects composites).IN (...)onto the sharded probe.scripts/start_pg_sharding_demo.sh+run_pg_sharding_demo.sh) on ports 16432/16433 exercising RANGE + LIST + cross-shard 2PC.sqlenginenow auto-selectsPOSTGRESQL2PC dialect when all backends arepgsql://.Stacked on #61.
Test results
./run_tests --gtest_brief=1→ 1344 passed, 40 skipped