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:
- Brand new partition rule checks, supporting more flexible partition expressions
- Fixed query timeout mechanism
- Supports dynamic modification of index granularity and false positive rate
- Loki log writing API supports configuring pipeline
Contributors
For the past two weeks, our community has been super active with a total of 137 PRs merged. 4 PRs from 2 individual contributors merged successfully and lots pending to be merged.
Congrats on becoming our most active contributors in the past 2 weeks:
👏 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#6390 Loki Write API supports configuring pipelines
When using the Loki protocol to write log data, you can specify the pipeline name used to process the log data through the x-greptime-pipeline-name
HTTP header, enabling flexible and efficient log processing.
db#6454 db#6444 Fix the MAX_EXECUTION_TIME
timeout calculation issue and the problem of it not taking effect in standalone mode
When using MySQL/PostgreSQL clients and JDBC connections for queries, users can set the MAX_EXECUTION_TIME
configuration to specify the query timeout. In the original implementation, there were issues with calculating the timeout that could prevent queries from terminating correctly after timing out. Additionally, timeout control was not effective in standalone mode. db#6454 and db#6444 fixed these issues and support disabling timeouts by setting MAX_EXECUTION_TIME
.
db#6431 New partition rule checker implementation
The partition rule checker is used to verify whether the user-input partition expressions are correct when creating tables. However, the original implementation of the partition rule checker in GreptimeDB is relatively simple and cannot cover certain rules, which may lead to misjudgments, such as:
CREATE TABLE test_table (
a INT,
b STRING,
ts TIMESTAMP TIME INDEX,
PRIMARY KEY (a, b)
)
PARTITION ON COLUMNS (a, b) (
a < 10,
a >= 10 AND b < 'a',
a >= 10 AND b >= 'a',
);
ERROR 1210 (HY000): (InvalidArguments): Unclosed value Int32(10) on column a
The partition rule checker has been re-implemented in db#6431, supporting a wider range of partition expressions.
db#6416 Supports modifying the granularity and false positive rate of indexes
Dynamic modification of index parameters is supported in db#6416, allowing users to modify the index granularity and false positive rate of column indexes through the ALTER TABLE
statement.
ALTER TABLE test_table MODIFY COLUMN value SET SKIPPING INDEX WITH(granularity = 2048, type = 'BLOOM', false_positive_rate = 0.01);
Good First Issue
Issue#5956 Support TLS connection to etcd on Metasrv
Metasrv supports storing cluster metadata in etcd, but currently does not support accessing etcd via a secure TLS connection. The goal of this issue is to support this feature to enhance the security of the cluster.
Keywords:TLS, etcd, Metasrv
Difficulty:Medium