Summary

Together with our global community of contributors, GreptimeDB continues to evolve and flourish as a growing open-source project. We are grateful to each and every one of you.

Below are the highlights among recent commits:

• Flat Format moves forward with range scan and write-path work
• Distributed query optimization: prune irrelevant Regions at the planning stage
• OTLP ingestion supports custom headers
• Sparse primary key encoding is up to 235% faster

Contributors

For the past two weeks, our community has been super active with a total of 122 PRs merged. 7 PRs from 7 individual contributors merged successfully and lots pending to be merged.

Congrats on becoming our most active contributors in the past 2 weeks:

• @Arshdeep54 db#6619
• @aaraujo db#6780
• @codephage2020 db#6818
• @SNC123 db#6757
• @WaterWhisperer db#6863
• @yihong0618 db#6704
• @zqr10159 db#6764

（Figure 1: New Contributors of GreptimeDB）

Highlights of Recent PRs

db#6505 High-cardinality-optimized Flat Format (ongoing)

Progress has been made across multiple PRs to push Flat Format forward: RecordBatch adaptation(db#6771, db#6786), range-scan functions(db#6817), and write-path integration(db#6866).

db#6752 Prune Regions by logical plan predicate

Regions that cannot satisfy the query predicate are skipped up front, reducing unnecessary scans and improving latency.

db#6777 Persist Metasrv internal metrics to internal tables

Makes critical cluster internals queryable via SQL for better monitoring and troubleshooting.

db#6773 Configurable headers for OTLP ingestion

Allows attaching custom headers when reporting metrics via OTLP to align with deployment requirements.

## Additional OTLP headers, only valid when using OTLP http
[logging.otlp_headers]
Authorization = "Bearer my-token"
Database = "My database"

db#6809 235% faster sparse primary key encoding

Substantial optimization of the sparse primary-key encoding path, reducing CPU overhead.

db#6816 Remote WAL replay checkpoints

Introduces replay checkpoints to bound startup replays, accelerating Datanode restarts in worst-case scenarios.

db#6764 Support to specify schema for Postgres KV backend

Adds a configuration option to choose the schema used by the Postgres KV backend.

Good First Issue

Issue#6760 Add profile signal configuration for OLTP protocols

Keywords: OLTP, Profiling

Difficulty: Simple