greptimedb

mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2026-08-24 23:18:25 +00:00

Files

T

discord9 40e02ff6b6 fix(query): restore columnar group-by for dictionary-encoded tags

Bump the pinned DataFusion fork from 452cb4b786 to its linear successor
4c8a6bf283. The successor preserves the existing Dictionary-literal
Substrait fix, includes the intervening join-cardinality overflow fix,
and adds DictionaryGroupValuesColumn support so dictionary-encoded group
keys can use the columnar grouping path instead of GroupValuesRows.

Add an end-to-end integration test that writes 1,200 rows to an
append-mode flat SST, groups its dictionary-encoded hostname tag by hour,
and checks all six ordered result tuples exactly. AggregateExec does not
expose the concrete GroupValues implementation through EXPLAIN or metrics;
direct DictionaryGroupValuesColumn path coverage remains in the pinned
DataFusion fork tests.

(cherry picked from commit d99b0df374)
Signed-off-by: discord9 <discord9@163.com>

2026-08-21 12:37:46 +08:00

fixtures

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

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

resources

feat: ingest jsonbench data through pipeline (#7312 )

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

src

feat(procedure): record event actor (#8849 )

2026-08-21 11:51:11 +08:00

tests

fix(query): restore columnar group-by for dictionary-encoded tags

2026-08-21 12:37:46 +08:00

Cargo.toml

chore!: gate soft-drop table behind the enterprise feature (#8747 )

2026-08-06 15:10:54 +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.