7c1009c00f
* feat: accept x-greptime-pipeline-name header on /events/logs The /events/logs (and /logs/ingest) endpoint previously only read the pipeline name from the `pipeline_name` query parameter, while the OTLP/Elasticsearch/Splunk log ingestion endpoints already accept it via the `x-greptime-pipeline-name` header. This inconsistency is unfriendly to users. Make `log_ingester` resolve the pipeline name from the `x-greptime-pipeline-name` header (and the deprecated `x-greptime-log-pipeline-name`), falling back to the query parameter. The header takes precedence, consistent with how other pipeline options (e.g. `x-greptime-pipeline-params`) outrank their query-parameter counterparts. Closes #6095 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: BootstrapperSBL <yvanwww01@gmail.com> * address review: prefer non-deprecated pipeline-name header When both pipeline-name headers are present, resolve the non-deprecated `x-greptime-pipeline-name` before the deprecated `x-greptime-log-pipeline-name`, and cover the precedence with a test. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: BootstrapperSBL <yvanwww01@gmail.com> --------- Signed-off-by: BootstrapperSBL <yvanwww01@gmail.com> Co-authored-by: BootstrapperSBL <yvanwww01@gmail.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
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 certificateserver.crt/server-key.pem- Server certificate for etcd-tls serviceclient.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.