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:

• Pipeline supports log filtering
• Support for retrieving current session query timeout through SELECT @@max_execution_time
• Optimize the user experience of Prometheus query_range compatibility API
• Improve the stability of flow tasks

Contributors

For the past two weeks, our community has been super active with a total of 115 PRs merged. 4 PRs from 3 individual contributors merged successfully and lots pending to be merged. Congrats on becoming our most active contributors in the past 2 weeks:

• @codephage2020 db#6517 db#6511
• @yihong0618 db#6559
• @zqr10159 greptimedb-ingester-java#90

🎆 Extending a warm welcome to GreptimeDB's second Advocator, @yihong0618, who officially joins our community! He will actively contribute to GreptimeDB's technical advocacy, community outreach, and developer ecosystem growth, collaborating with the community to drive the project's advancement and widespread adoption!

（Figure 1: GreptimeDB Advocator Announcement）

👏 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#6502 Pipeline Supports Filter Processor

Pipeline has added a filter processor for filtering logs. Users can use this processor to filter out unwanted logs. The following example can keep only logs containing "John".

processors:
  - date:
      field: time
      formats:
        - "%Y-%m-%d %H:%M:%S%.3f"
  - filter:
      field: name
      targets: 
        - John
transform:
  - field: name
    type: string
  - field: time
    type: time
    index: timestamp

Filter processor accepts the following parameters:

1. field (or fields): The field(s) to compare against, can be one or multiple; if any variable matches, the condition is satisfied and filtering is executed.
2. mode (optional): Defaults to simple, which means simple string matching. This field is for future extension use.
3. match_op (optional): If the mode is simple, this can be set to in or not_in. Default is in.
4. case_insensitive (optional): Defaults to true
5. targets: List of target strings for comparison

db#6511 db#6517 Support Retrieving max_execution_time value through querying system variables

Now you can retrieve the current session's query timeout using SELECT @@max_execution_time or SELECT @@session.max_execution_time statements:

SET max_execution_time = 9000;
SELECT @@max_Execution_time;
+----------------------+
| @@max_execution_time |
+----------------------+
| 9000                 |
+----------------------+

db#6474 Sort the Results of range_query API before Returning to Optimize User Grafana Experience

Previously, GreptimeDB did not sort results by default in the Prometheus range_query API. If a Grafana panel's PromQL involved binary operators, users might encounter inconsistent chart display issues. In such cases, users needed to manually add a sort Transform for the panel in Grafana. Now GreptimeDB will sort results by default.

db#6538 db#6495 db#6551 Fixed Several Flow Issues to Improve the Stability of Flow Service

• Optimized task retry logic
• Fixed address cache update issues
• Optimized window calculation performance

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：etcd、Metasrv、TLS
• Difficulty：Medium