Summary

Development period: 2025-12-29 - 2026-01-11

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 from recent commits:

• Region repartitioning procedure integrated into DDL operations
• Vector index building enables faster similarity search

We recommend users running previous versions to upgrade to the latest version for an improved experience.

Contributors

Over the past two weeks, 11 contributors merged a total of 39 PRs.Among them, 1 individual contributors contributed 2 PRs.

Congrats to our most active individual contributors:

• @Standing-Man db#7506 db#7476

Highlights of Recent PRs

Region Repartition Procedure

A series of PRs landed the complete region repartitioning feature:

• db#7534: Implements the region allocation phase, including WAL option selection, region route allocation, and metadata updates
• db#7509: Adds manifest remapping and apply staging manifest handlers on datanodes, and the corresponding meta-srv procedure states
• db#7548: Hooks repartition into DdlManager so ALTER TABLE can submit and track repartition procedures

This feature is expected to ship in the upcoming RC1 release later this month.

db#7468 feat: impl vector index building

Implements vector index building infrastructure using HNSW algorithm via USearch, enabling vector index construction during SST flush and compaction.

Good First Issue

Issue#7314 Feature Request: Add built-in daemon mode to keep GreptimeDB running independently of shell sessions

Add a --daemon CLI flag to allow GreptimeDB to run as a background process independent of shell sessions, similar to Redis's daemonize option.

Keywords: CLI, daemon mode

Difficulty: Medium

Issue#6095 Make /events/logs to accept x-greptime-pipeline-name header

The OTEL protocols accept x-greptime-pipeline-name as a pipeline name, but /events/logs does not. This inconsistency is unfriendly to users. This enhancement would align the /events/logs endpoint with the OTEL protocol behavior.

Keywords: API, HTTP, OTEL, pipeline

Difficulty: Easy