9d08f2532a
* wip: steppable aggr fn Signed-off-by: discord9 <discord9@163.com> * poc: step aggr query Signed-off-by: discord9 <discord9@163.com> * feat: mvp poc stuff Signed-off-by: discord9 <discord9@163.com> * test: sqlness Signed-off-by: discord9 <discord9@163.com> * chore: import missing Signed-off-by: discord9 <discord9@163.com> * feat: support first/last_value Signed-off-by: discord9 <discord9@163.com> * fix: check also include first/last value Signed-off-by: discord9 <discord9@163.com> * chore: clean up after rebase Signed-off-by: discord9 <discord9@163.com> * feat: optimize yes! Signed-off-by: discord9 <discord9@163.com> * fix: alias qualifled Signed-off-by: discord9 <discord9@163.com> * test: more testcases Signed-off-by: discord9 <discord9@163.com> * chore: qualified column Signed-off-by: discord9 <discord9@163.com> * chore: per review Signed-off-by: discord9 <discord9@163.com> * fix: case when can push down Signed-off-by: discord9 <discord9@163.com> * feat: udd/hll_merge is also the same Signed-off-by: discord9 <discord9@163.com> * fix: udd/hll_merge args Signed-off-by: discord9 <discord9@163.com> * tests: fix sqlness Signed-off-by: discord9 <discord9@163.com> * tests: fix sqlness Signed-off-by: discord9 <discord9@163.com> * fix: udd/hll merge steppable Signed-off-by: discord9 <discord9@163.com> * chore: per review Signed-off-by: discord9 <discord9@163.com> * test: REDACTED Signed-off-by: discord9 <discord9@163.com> * refactor: per review Signed-off-by: discord9 <discord9@163.com> * refactor: more formal transform action Signed-off-by: discord9 <discord9@163.com> * feat: support modify child plan too Signed-off-by: discord9 <discord9@163.com> --------- Signed-off-by: discord9 <discord9@163.com>
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 -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
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 🥳!