discord9 da27d115ca feat(query): let a region input travel as a plan when regions are in process ...

A plan holding a node with no Substrait serializer was always cut at that node,
because the analyzer asks whether a plan encodes before it asks whether a node
commutes with the region split. That is right for a region reached over the wire:
the plan is encoded into the request and has to decode on the other side.

Standalone does not use that path. Its region server is the one built in the same
process, its query handler passes the request straight to `RegionServer::handle_read`,
and the plan stays a `LogicalPlan` from the frontend to the region. Encoding it is
work nobody reads, and refusing to place a node because it cannot be encoded
refuses a plan that would have travelled intact.

So the engine now knows whether its regions are reached in process, and the
encodability gate applies only when they are not. The capability is set where it
can be stated truthfully - the standalone bootstrap, which creates both the
frontend and the region server it reads - and it defaults to false everywhere
else, so an ordinary build and every other deployment keeps today's behaviour
byte for byte.

Skipping the gate skips one early return and adds no reason to expand:
`Categorizer::check_plan` still runs and still decides, and a plan that does not
encode for any other reason still expands at the node that caused it. Two tests
hold those two halves apart.

Signed-off-by: discord9 <discord9@163.com>

2026-10-23 19:57:38 +08:00

..

src

feat(query): let a region input travel as a plan when regions are in process

2026-10-23 19:57:38 +08:00

AGENTS.md

feat(frontend): retry transient distributed write failures (#9543)

2026-10-13 14:51:35 +00:00

Cargo.toml

perf: cache OTLP trace service and operation writes (#9432)

2026-10-10 02:45:43 +00:00