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:

• A metadata reconciler has been introduced to reconcile metadata differences between Metasrv and the Region Manifest

• Make OTLP metric compatible with Prometheus/PromQL

• Proposed key RFCs: Partitioning, Compatibility Testing Framework

• Support more PromQL functions:absent, clamp, clamp_min, clamp_max, pi, deg, sgn, rad

Contributors

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

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

• @Arshdeep54 db#6422
• @Damian972 docs#2003
• @linyihai db#6421
• @lyang24 db#6466
• @kemingy db#6634
• @yihong0618 db#6637 db#6587 db#6570 db#6569 db#6560

👏 Welcome @Damian972 @kemingy to the community as a new contributor with a successfully merged PR, and more PRs from other individual contributors are waiting to be merged.

（Figure 1: New Contributors of GreptimeDB）

👏 A big THANK YOU to all our members and contributors! It is people like you who are making GreptimeDB a great product. Let's build an even greater community together.

Highlights of Recent PRs

db#6634 Upgrade greptime-sqlparser to avoid stack overflow crash during SQL parsing

Upgraded the greptime-sqlparser dependency to fix a stack overflow crash caused by excessively long WHERE clauses during SQL parsing, thereby improving GreptimeDB’s stability.

db#6543 Make OTLP metric compatible with PromQL

OTLP metrics are now compatible with the Prometheus data model. You can treat OTLP metrics as Prometheus metrics and query them directly with PromQL, while this PR maintains complete backward compatibility.

db#6529 Supports more DB options

Support setting more options at the database-level, which simplify repeated configuration when creating tables. For example:

CREATE DATABASE mydb WITH (
       ttl = '1h',
       'memtable.type'='partition_tree',
       'append_mode'='false',
       'merge_mode'='last_non_null',
       'compaction.type' = 'twcs',
       'compaction.twcs.time_window' = '1h',
       'skip_wal'='true');

Note: If you explicitly declare an option with the same name when creating a table later, the table-level options will override the database-level options.

db#6584 #6588 #6612 #6613 #6614 Introduce reconcile procedure

A metadata reconciler has been introduced to reconcile metadata differences between Metasrv and the Region Manifest. Three new admin functions have been added:

• admin reconcile_catalog(resolve_strategy, parallelism): reconciles all tables in the current catalog
• admin reconcile_database(database_name,resolve_strategy, parallelism): reconciles all tables in the current schema
• admin reconcile_table(table_name,resolve_strategy, parallelism): reconciles a specific table

When database metadata anomalies occur, attempt recovery using the aforementioned admin method.

Good First Issue

Issue#6334 Improve KILL Support for INSERT INTO SELECT Queries

• Keyword: Query Engine

• Difficulty: Medium

Issue#6621 Add config option to host on subpath

• Keyword: Dashboard, Axum

• Difficulty: Simple