mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2026-09-22 21:25:41 +00:00

Files

T

Dennis Zhuang a164c4a66d fix(promql): clamp extrapolation before snapping a counter to zero

Prometheus clamps `durationToStart` to half an average interval once the
first sample is past the extrapolation threshold, and only then lets the
counter zero-snap shorten it further, so the snap can never lengthen the
leading extrapolation. Running the snap first let it rescue a duration
the clamp should have cut, and `rate` and `increase` over-extrapolated
to the left. For samples 1@0s and 2@1s in a 4s window at 1s, upstream
gives 0.375 and this returned 0.5.

`extrapolation_matches_prometheus_on_seeded_windows` carries a
line-by-line port of upstream `extrapolatedRate` as an oracle and diffs
it against the UDF over seeded windows, so the order stays pinned.
`factor` also picked up upstream's guard against a zero sampled
interval, which previously divided by zero.

Two sqlness results move, both verified against the upstream algorithm.

Signed-off-by: Dennis Zhuang <killme2008@gmail.com>

2026-09-11 20:47:12 +08:00

cases

fix(promql): clamp extrapolation before snapping a counter to zero

2026-09-11 20:47:12 +08:00

compat

refactor: restructure sqlness to support multiple envs and extract common utils (#7066 )

2025-10-11 06:34:17 +00:00

compatibility

feat(mito2): introduce TWCS active window compaction (#9011 )

2026-09-09 13:02:26 +00:00

conf

feat: synthesize OTLP resource descriptor for the semantic entity graph (#8904 )

2026-08-25 13:08:44 +00:00

data

feat: support headerless CSV copy from (#8233 )

2026-06-04 12:04:15 +00:00

perf

perf(promql): avoid per-window allocations in simple range functions (#9104 )

2026-09-11 11:59:45 +00:00

runner

chore: update mysql test drivers and lru (#8868 )

2026-08-13 10:58:29 +00:00

upgrade-compat

feat!: improve mysql/pg compatibility (#7315 )

2025-12-01 20:41:14 +00:00

README.md

refactor: restructure sqlness to support multiple envs and extract common utils (#7066 )

2025-10-11 06:34:17 +00:00

README.md

Sqlness Test

Sqlness manual

Case file

Sqlness has two types of file:

.sql: test input, SQL only
.result: expected test output, SQL and its results

.result is the output (execution result) file. If you see .result files is changed, it means this test gets a different result and indicates it fails. You should check change logs to solve the problem.

You only need to write test SQL in .sql file, and run the test.

Case organization

The root dir of input cases is tests/cases. It contains several subdirectories stand for different test modes. E.g., standalone/ contains all the tests to run under greptimedb standalone start mode.

Under the first level of subdirectory (e.g. the cases/standalone), you can organize your cases as you like. Sqlness walks through every file recursively and runs them.

Kafka WAL

Sqlness supports Kafka WAL. You can either provide a Kafka cluster or let sqlness to start one for you.

To run test with kafka, you need to pass the option -w kafka. If no other options are provided, sqlness will use conf/kafka-cluster.yml to start a Kafka cluster. This requires docker and docker-compose commands in your environment.

Otherwise, you can additionally pass the your existing kafka environment to sqlness with -k option. E.g.:

cargo sqlness bare -w kafka -k localhost:9092

In this case, sqlness will not start its own kafka cluster and the one you provided instead.

Run the test

Unlike other tests, this harness is in a binary target form. You can run it with:

cargo sqlness bare

It automatically finishes the following procedures: compile GreptimeDB, start it, grab tests and feed it to the server, then collect and compare the results. You only need to check if the .result files are changed. If not, congratulations, the test is passed 🥳!