mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2026-11-15 07:17:01 +00:00

Files

T

discord9 c703229c16 refactor(series): hold the frame layout marker at one value

The series frame is the native PromQL path's internal transport and has never shipped, so its
layout marker can only ever tell two binaries of different workspace revisions apart - and a
workspace builds one revision. Carrying a revision number in it bought nothing and could only make
a stale local binary fail against a freshly built one, so it goes back to a single value and stays
there.

The reader still refuses a frame that declares any other value: that check is what turns a
mismatched producer into an error instead of values decoded under the wrong columns. Only the value
it expects changes.

The two wire fixtures under tests/compatibility/wire/ are renamed to match and their literal
metadata maps retargeted; the cases that exist to be the wrong layout now use the value that is not
current, so they still test what they were written to test.

Verified: datatypes+common-query 565 passed / 0 failed; promql+query 2192 passed / 0 failed / 2
skipped; cargo fmt --check clean.

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

2026-11-06 11:57:32 +08:00

cases

feat(promql): preserve scan parallelism through native frame boundaries (#10055 )

2026-11-04 14:12:56 +08:00

compatibility

refactor(series): hold the frame layout marker at one value

2026-11-06 11:57:32 +08: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: compare several images in one object store WAL S3 benchmark run (#9691 )

2026-10-23 14:43:10 +08: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 🥳!