greptimedb

mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2026-10-15 00:12:29 +00:00

Files

T

Dennis Zhuang 39bba171c9 fix(otlp): guard descriptor writes with semantic ownership markers

A pre-existing schema-compatible table named otel_resource_info would
silently receive descriptor rows while its missing semantic stamps kept
it out of the entity graph. The descriptor write now requires the
auto-created table's ownership markers (mito engine + signal_type +
source + metric.type=info + metadata_quality=declared) and otherwise
degrades to the partial-success warning; the entity-graph gate for the
otel whitelist likewise requires metric.type=info, so a user table
stamped with only signal/source no longer picks up implicit
declarations.

Also fold the descriptor write cost into the response and surface the
degrade warning through the otel-arrow BatchStatus status_message.
Integration tests pin the full marker set on auto-create and that an
existing owned descriptor keeps accepting writes without degrading —
a missing marker would otherwise silently stop every descriptor write
after the first request.

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

2026-08-17 23:43:27 +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-14 09:36:01 +00:00

tests

fix(otlp): guard descriptor writes with semantic ownership markers

2026-08-17 23:43:27 +08:00

Cargo.toml

chore: update mysql test drivers and lru (#8868 )

2026-08-13 10:58:29 +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.