greptimedb

mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2026-11-14 23:06:59 +00:00

Files

T

Dennis Zhuang 1be0df046c feat(promql): compile and run set operators natively

Bind `and`, `or` and `unless` (with `on`/`ignoring`) to a new
`NativeExpr::Set` node instead of refusing them. The node runs the
existing MATCH-SET kernel through the binary runtime, which retains both
operands until the input ends, so a set operation reads every series of
both sides in one execution.

The set kernel now reports its workspace like the binary kernel does:
kept rows, the filter side's match groups, the sort and the merge are
charged to the node's reservation.

The compiler refuses a fill value on a set operator, which Prometheus
rejects and the parser accepts, and sides with different field counts.
Same-table set operations over two scans take the existing two-scan
native route.

Signed-off-by: Dennis Zhuang <killme2008@gmail.com>

2026-10-26 16:23:05 +08:00

fixtures

fix(mito2): compare primary key ranges across schema versions (#9205 )

2026-09-20 14:30:12 +00:00

resources

feat: ingest jsonbench data through pipeline (#7312 )

2026-01-05 12:12:34 +00:00

src

feat(promql): compile and run set operators natively

2026-10-26 16:23:05 +08:00

tests

test(promql): keep the frame output tests lint-clean

2026-10-26 14:51:19 +08:00

AGENTS.md

test: make export chunk deletion failure deterministic (#9291 )

2026-09-22 04:58:58 +00:00

Cargo.toml

fix(promql): stream evaluated frames with batch-level backpressure

2026-10-26 14:51:19 +08:00

README.md

feat: add TLS support for mysql backend (#6979 )

2025-09-16 13:46:37 +00:00

README.md

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 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.