greptimedb

mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2026-11-13 22:36:57 +00:00

Files

T

dennis zhuang 2714687ab7 feat(otlp): add v1 schema for auto-created OTLP log tables (#10207 )

* feat(otlp): add v1 schema for auto-created OTLP log tables

New tables created by direct OTLP logs ingestion get a v1 built-in schema:
service_name tag from resource service.name ahead of scope_name in the
primary key, a skipping index on trace_id, and event_name and
observed_timestamp fields. The table is marked with
table_data_model=greptime_log_v1. Existing tables without the marker keep
the legacy schema.

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

* refactor(otlp): share resource service.name parsing between logs and traces

Log tables now derive service_name with the same rules as trace spans, so
both signals agree on the value used to correlate them. The integration test
writes twice to cover the existing v1 table path.

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

---------

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

2026-11-06 02:40:23 +00: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

fix(catalog): use advertised peer address as process identity (#10153 )

2026-11-04 18:18:38 +00:00

tests

feat(otlp): add v1 schema for auto-created OTLP log tables (#10207 )

2026-11-06 02:40:23 +00:00

AGENTS.md

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

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

Cargo.toml

feat: COPY FROM STDIN for postgres interface (#9297 )

2026-10-26 07:08:12 +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.