โœ•

Join us at two must-attend conferences this summer and claim your exclusive SWAG! ๐ŸŽ

IOT TECH EXPO, June 5-6 in Santa Clara! Booth 270 | DATA + AI SUMMIT, June 11-13 in San Francisco! Booth e12

โœ•
Skip to content
On this page

Subscribe to our newsletter

Get the latest dates and news about GreptimeDB.
Biweekly
โ€ข
December 27, 2023

Biweekly Report - Explore More SQL Examples in the GreptimeDB Playground

A recap of the past two-weeks progress and changes happened on GreptimeDB.

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.

In the past two weeks, we have made steady progress. Below are some highlights:

  • Complete remote WAL's basic framework;

  • HTTP SQL API now features the capability to return SQL query results in the InfluxDB v1 format;

  • Support concurrent Parquet acquisition to improve query performance;

  • The Inverted Index and Metric Engine are under full development.

Contributors โ€‹

For the past two weeks, our community has been super active with a total of 56 PRs merged. 5 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:

๐Ÿ‘ Welcome our new contributor @Dysprosium to our community, and congratulations on successfully merging his first PR.

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 PR โ€‹

#2917 HTTP SQL API now features the capability to return SQL query results in the InfluxDB v1 format โ€‹

We support returning the query in influxdb v1 result format, for example, we can send the following request: http://ip:port/v1/sql?db=public&format=influxdb_v1&epoch=ns. The epoch precision can be one of [ns,u,ยต,ms,s].

#2935 Added some tables to information_schema โ€‹

Introduce information_schema, which provides an ANSI-standard way of viewing system metadata, and we add engines, column_privileges and column_statistics to information_schema now.

For example, we can view the system's engines through the following SQL statement.

sql
mysql> select * from engines;
+--------+---------+-------------------------------------+--------------+------+------------+
| engine | support | comment                             | transactions | xa   | savepoints |
+--------+---------+-------------------------------------+--------------+------+------------+
| mito   | DEFAULT | Storage engine for time-series data | NO           | NO   | NO         |
+--------+---------+-------------------------------------+--------------+------+------------+

#2930 Allowed initializing regions in background โ€‹

This feature allows users to initiate the startup process for all regions in the background, without delaying or blocking the startup process. As a result, users can start using the database more quickly.

#2959 Supported concurrent fetching of parquet files with ranges โ€‹

Previously, we obtained the parquet file sequentially, and now it is optimized for concurrent acquisition. Under TSBS benchmark, some scenarios have an improvement of more than 175%.

Good first issue โ€‹

#2931 Information_schema improvements

#2995 Make the stdout log appender configurable

New Things โ€‹

Play more SQL statement in PLAYGROUND now โ€‹

The 'Getting Started' documentation has been updated with new data sources, along with the inclusion of new Range Query SQL statements. Additionally, a weather-related example demonstrating the Range Query has been added for enhanced clarity and practical application.

Try now: https://greptime.com/playground/

Join our community

Get the latest updates and discuss with other users.

Subscribe to our newsletter

Get the latest dates and news about GreptimeDB.