Files
greptimedb/src/query
discord9 feef5164e2 fix(query): plan a data-free statement and a zero-match discovery natively (#10224)
Three refusals kept statements off the native route in a distributed
deployment, and one of them raised an Internal error rather than falling back:

- `remote_native_raw_plan_supported` required a `RawSeriesSource` somewhere in
  the plan, so a statement that reads no table was re-planned without native
  execution and answered with legacy column names. The gate now also admits a
  `FusedSeries` chain whose leaves are all the typed empty input - followed
  through fused nodes only, so a scan, a raw source or any other extension
  still rejects - and the exact `strip_tsid_column` projection over such a
  chain.
- A nameless selector that matches no metric produced a typed empty input, and
  on the distributed route that input fell through to "a prepared selector has
  no metric name". It now stays that input on both routes: never wrapped in a
  raw source, never bound to a metric.
- A segmented shape such as `sort({job="api"})` did not recognize the empty
  child as an already-prepared explicit-frame input, so it declined. It is
  recognized next to a raw source now.

The empty predicate checks the declared frame rather than only the
`EmptyRelation` variant, so the guard's narrowness rests on a typed check.

Tests cover `time()`, `vector(1)`, label rewrites including one that
synthesizes `__tsid`, and `{job="api"}` / `sort` / `sum` / `absent` with no
authorized metric, asserting native admission, the declared frame schema,
`metric_name: None` and the actual rows and labels - including a two-datanode
distributed case.

Signed-off-by: discord9 <discord9@163.com>
2026-11-06 18:11:05 +08:00
..