A native rows result now always declares `__name__`, a nullable `Utf8` column appended after the labels and marked as the metric name, and each row carries the name of the series it was read from. A row whose value is computed rather than read (a math kernel, a folding aggregate, a range function) carries null there. The name is part of what the statement answers, not of how a response is displayed: the walk that derives a node's tags reports the name of a discovered source and of an `or` unconditionally, so `sum by (__name__)` groups on the identity of the series rather than collapsing every series into one group. `with_row_name_column` appends the column when the root is a samples root. It moves an existing name column to the end rather than adding a second one, because neither a set operation nor a discovered source leaves an existing name last: `or` keeps the order of the left operand and appends only the tags of the right side it has not seen, while a discovered source sorts its tags, which puts the name wherever its bytes fall. Every rows layout then answers one order - the time index, the value fields, the labels, then the name. A `label_replace(..., "__name__", ...)` result is therefore not declared twice, and a scalar root keeps its two columns. The collision check runs after the column is appended, so a name that would clash with a label still declines the layout, and a split's terminal schema declares the column while the frame producers keep the tags they were compiled with. A CTE answered natively publishes the column too, after the existing planner's columns and only when the answer declares one: `publish_legacy_schema` keeps the metadata-carrying name column out of its type-based pairing, so a label cannot claim it, and validates the published schema column by column. `abs(a or b)` now reports no `__name__` at all instead of the statement's name on every row: the operator drops the name, so the declared column's values are null. Shapes that keep the name (plain selection, filtering comparison, `or`, `topk`/`sort`, `first/last_over_time`, `sum by (__name__)`) carry it per row. Signed-off-by: discord9 <discord9@163.com>
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/.
-
Start TLS-enabled etcd:
cd tests-integration/fixtures docker compose up etcd-tls -d -
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 certificateserver.crt/server-key.pem- Server certificate for etcd-tls serviceclient.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.