Repository navigation

Plan a V2 scan as a chain of planners from one prepared scan - #10707

Open

joseph-isaacs wants to merge 12 commits into

developfrom

ji/scan-v2-chain-2-planners

Open

Plan a V2 scan as a chain of planners from one prepared scan#10707
joseph-isaacs wants to merge 12 commits into
developfrom
ji/scan-v2-chain-2-planners

Commits on Oct 23, 2026
- Plan a V2 scan as a chain of planners from one prepared scan
  
  joseph-isaacs
  and
  claude
  committed
  c56ec58
- Optimize a zoned data plan to its data child
  
  joseph-isaacs
  and
  claude
  committed
  8e106ac
- Share one V2 scan cache per file across DataFusion partitions
  
  joseph-isaacs
  and
  claude
  committed
  38f6a81
- Drive a V2 scan's run from its stream, with compute on spawn_cpu
  
  joseph-isaacs
  and
  claude
  committed
  6894be0
- Build a prune planner with the planner it continues into
  
  joseph-isaacs
  and
  claude
  committed
  5a66bc1
- Spawn a scan's chunks as independent planners and run them beside each other
  
  joseph-isaacs
  and
  claude
  committed
  a74502f
- Dedup a planner's IO hints with a set
  
  joseph-isaacs
  and
  claude
  committed
  52daa27
- Run a V2 scan's chunks beside each other only as far as the engine does not
  
  joseph-isaacs
  and
  claude
  committed
  26c4265
- Link the run driver by its imported name in the V2 module doc
  
  joseph-isaacs
  and
  claude
  committed
  c441bc4
- Merge remote-tracking branch 'origin/develop' into ji/scan-v2-chain-2-planners
  
  claude
  authored and
  joseph-isaacs
  committed
  1cb2d99
- Pass an execution context to ListArray::try_new in the nested empty list test
  
  joseph-isaacs
  and
  claude
  committed
  33a5b24
- Merge remote-tracking branch 'origin/develop' into ji/scan-v2-chain-2-planners
  
  joseph-isaacs
  and
  claude
  committed
  9f8bf1c

Commits

Commits on Oct 23, 2026