Files
greptimedb/tests/compatibility/ci.toml
T
discord9 a1be266c3c fix(promql): ignore histogram samples in scalar() and share one kernel (#10426)
* fix(promql): ignore histogram samples in scalar() and share one kernel

Prometheus' funcScalar counts only float samples: histogram samples are ignored silently,
so they neither supply a value nor make a point hold more than one element. The select
kernel rejected them instead, while the native ScalarOf runtime kept its own inline loop
that ignored them, so scalar(histogram_metric) answered differently depending on the
route.

The kernel now ignores histogram samples and the runtime calls it, deleting the inline
copy. A point with one float answers that float, with only histograms or with several
floats answers the Go NaN.

The kernel builds its answer as one dense run over the grid: a Vec<f64> seeded with the
Go NaN, where the first float at a point writes its value and a second writes NaN back,
plus the counts the caller already reserves. That buffer becomes the result's Float64Array
by move, so the per-point peak is the 8 bytes of values plus 1 of counts the reservation
already counts. Staging through Vec<Option<f64>> and GridSeriesBuilder would have held
about 33 bytes per point against a 9-byte reservation.

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

* refactor(promql): resolve the evaluation grid once in scalar()

grid_points already resolves and validates the grid, so asking for the schema's grid again
right after could only disagree with what was just checked.

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

* chore(compat): move the from-versions window to v1.3.1

v1.3.1 has published release assets, so the compatibility check asks for it and fails on
every branch that still names v1.3.0.

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

---------

Signed-off-by: discord9 <discord9@163.com>
2026-11-16 14:57:32 +08:00

13 lines
597 B
TOML

# Compatibility CI version window.
#
# The PR window keeps the latest patch in each of the two most recent stable
# minor lines whose tags have published release assets. Exact =vX.Y.Z
# `from_range` anchors in case.toml are validated by --check-anchors and
# exercised by nightly runs (--nightly-window); they are not retained in the PR
# window. Run .github/scripts/update-compat-versions.py --update --published-only
# after release tags land.
from_versions = ["v1.2.1", "v1.3.1"]
# Recent releases that must be able to reopen tables written by the PR build.
downgrade_to_versions = ["v1.1.4"]