greptimedb

mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2026-09-12 16:32:16 +00:00

Files

T

dennis zhuang 60899d19ee perf(servers): defer Prometheus sample value formatting to serialization (#9091 )

Building a matrix response allocated one `String` per sample while the
record batches were scanned, then dropped it after the JSON body was
written. Keep the `f64` in `PromSampleValue::Number` instead and format
it with ryu while serializing, so no per-sample string is allocated.

`PromSampleValue::Text` keeps values parsed from a JSON body, so
deserializing and re-serializing a response is unchanged. Vector and
scalar results still expose `String`, since they hold a single sample.

Signed-off-by: Dennis Zhuang <xzhuang@greptime.com>

2026-09-10 04:20:57 +00:00

fixtures

test: renew etcd TLS certificates (#8956 )

2026-08-26 06:15:37 +00:00

resources

feat: ingest jsonbench data through pipeline (#7312 )

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

src

perf(promql): push down last row for instant queries (#9034 )

2026-09-09 12:38:52 +00:00

tests

perf(servers): defer Prometheus sample value formatting to serialization (#9091 )

2026-09-10 04:20:57 +00:00

Cargo.toml

fix: prevent catalog testing feature from leaking into production builds (#9063 )

2026-09-08 07:35:18 +00: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.