Files
greptimedb/tests-integration
discord9 feef5164e2 fix(query): plan a data-free statement and a zero-match discovery natively (#10224)
Three refusals kept statements off the native route in a distributed
deployment, and one of them raised an Internal error rather than falling back:

- `remote_native_raw_plan_supported` required a `RawSeriesSource` somewhere in
  the plan, so a statement that reads no table was re-planned without native
  execution and answered with legacy column names. The gate now also admits a
  `FusedSeries` chain whose leaves are all the typed empty input - followed
  through fused nodes only, so a scan, a raw source or any other extension
  still rejects - and the exact `strip_tsid_column` projection over such a
  chain.
- A nameless selector that matches no metric produced a typed empty input, and
  on the distributed route that input fell through to "a prepared selector has
  no metric name". It now stays that input on both routes: never wrapped in a
  raw source, never bound to a metric.
- A segmented shape such as `sort({job="api"})` did not recognize the empty
  child as an already-prepared explicit-frame input, so it declined. It is
  recognized next to a raw source now.

The empty predicate checks the declared frame rather than only the
`EmptyRelation` variant, so the guard's narrowness rests on a typed check.

Tests cover `time()`, `vector(1)`, label rewrites including one that
synthesizes `__tsid`, and `{job="api"}` / `sort` / `sum` / `absent` with no
authorized metric, asserting native admission, the declared frame schema,
`metric_name: None` and the actual rows and labels - including a two-datanode
distributed case.

Signed-off-by: discord9 <discord9@163.com>
2026-11-06 18:11:05 +08:00
..

Setup tests for multiple storage backend

To run the integration test, please copy .env.example to .env in the project root folder and change the values on need.

Take s3 for example. You need to set your S3 bucket, access key id and secret key:

# Settings for s3 test
GT_S3_BUCKET=S3 bucket
GT_S3_REGION=S3 region
GT_S3_ACCESS_KEY_ID=S3 access key id
GT_S3_ACCESS_KEY=S3 secret access key

Run

Execute the following command in the project root folder:

cargo test integration

Test s3 storage:

cargo test s3

Test oss storage:

cargo test oss

Test azblob storage:

cargo test azblob

Setup tests with Kafka wal

To run the integration test, please copy .env.example to .env in the project root folder and change the values on need.

GT_KAFKA_ENDPOINTS = localhost:9092

Setup kafka standalone

cd tests-integration/fixtures

docker compose -f docker-compose.yml up kafka

Setup tests with etcd TLS

This guide explains how to set up and test TLS-enabled etcd connections in GreptimeDB integration tests.

Quick Start

TLS certificates are already at tests-integration/fixtures/etcd-tls-certs/.

  1. Start TLS-enabled etcd:

    cd tests-integration/fixtures
    docker compose up etcd-tls -d
    
  2. Start all services (including etcd-tls):

    cd tests-integration/fixtures
    docker compose up -d --wait
    

Certificate Details

The checked-in certificates include:

  • ca.crt - Certificate Authority certificate
  • server.crt / server-key.pem - Server certificate for etcd-tls service
  • client.crt / client-key.pem - Client certificate for connecting to etcd-tls

The server certificate includes SANs for localhost, etcd-tls, 127.0.0.1, and ::1.

Regenerating Certificates (Optional)

If you need to regenerate the etcd certificates:

# Regenerate certificates (overwrites existing ones)
./scripts/generate-etcd-tls-certs.sh

# Or generate in custom location
./scripts/generate-etcd-tls-certs.sh /path/to/cert/directory

If you need to regenerate the mysql and postgres certificates:

# Regenerate certificates (overwrites existing ones)
./scripts/generate_certs.sh

# Or generate in custom location
./scripts/generate_certs.sh /path/to/cert/directory

Note: The checked-in certificates are for testing purposes only and should never be used in production.