mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2026-10-25 13:22:30 +00:00

Files

T

fengyue-xve 0ce6729b40 test(promql): cover label_replace normalization with distinct series (#9485 )

The duplicate-label-set rejection must not fire when a label rewrite keeps
every series distinct through another label. Normalizing mixed histogram
boundary representations (`10.0` -> `10`) while `instance` still differs is
the false positive reported in #9444. The check already accounts for it
since it became a per-timestamp row count instead of a planning-time
rejection, but no fixture covered the positive case. Add one, together
with the aggregation variant that produces a genuine duplicate and must
still fail.

Signed-off-by: fengyue-xve <1759519137@qq.com>
(cherry picked from commit 764ab8bc1a)
Signed-off-by: WenyXu <wenymedia@gmail.com>

2026-10-12 12:49:21 +00:00

cases

test(promql): cover label_replace normalization with distinct series (#9485 )

2026-10-12 12:49:21 +00:00

compatibility

feat: export Metric snapshots with packed Parquet objects (#9382 )

2026-09-28 15:22:02 +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

ci: add optional AWS runners for observability benchmarks (#9322 )

2026-09-23 12:46:31 +00:00

runner

fix(client): complete transport lane isolation (#9030 )

2026-09-28 04:39:20 +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 🥳!