โœ•

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 16, 2022

Biweekly Report (Nov.24 - Dec.9) โ€“ Allowing S3 Storage

A recap of the past one-month progress and changes happened on GreptimeDB

Biweekly Report (Nov.24 - Dec.9) โ€“ Allowing S3 Storage โ€‹

December 15, 2022 ยท 6 min read

Since open-sourced on Nov.15, the GreptimeDB community has merged 21 PRs from 10 contributors. That's nearly 25% of the whole project. What a productive month! This article updates two of the good first issues that we are working on and two of the highlighted features.

Introduction โ€‹

It's only been three weeks and the community has already received lots of attention and powerful support from developers scattered around the world. Their talent and passion took us by surprise and strengthened our belief in open source.

Biweekly Reports will be a series of quick reports that update our progress regularly. We hope, in this way, members and friends could understand what the project is doing and how they would participate in the GreptimeDB community.

Here are also some good examples of our issue pools. They would be perfect for newcomers, so please have faith in yourself and join us right away!

Join us at github.com

Contributors list: (In alphabetical order) โ€‹

@azhsmesos @DiamondMofeng @dongxuwang

@e1ijah1 @francis-du @lbt05

@lizhemingi @morigs @SSebo @Xuanwo

A big THANK YOU for the generous and brilliant contributions! It is people like you who are making GreptimeDB a great product. Let's keep up the good work!

Join us at github.com

Good first issue โ€‹

Issue #667 (Closed) โ€‹

Link๏ผšhttps://github.com/GreptimeTeam/greptimedb/issues/667

Issue description:

When we define TIME INDEX column, for example CREATE TABLE SQL:

SQL
CREATE TABLE system_metrics (
    host STRING,
    idc STRING,
    ts TIMESTAMP NOT NULL,
    PRIMARY KEY(host, idc),
    TIME INDEX(ts)
);

there are two special column specifications: PRIMARY KEY and TIME INDEX. The first one is used to define primary keys (or tags in some systems), and the second is to define which column is the special timestamp column.

For TIMESTAMP column, a simplification is to change the grammar to:

SQL
ts TIMESTAMP TIME INDEX,

By doing so, it

  • need not to write NOT NULL, this is implied by TIME INDEX keywords
  • need not to specify TIME INDEX in another line

GreptimeDB now supports both of these two grammar rules. Users can choose one of them according to their preference.

Issue #602 (Help Wanted) โ€‹

Link: https://github.com/GreptimeTeam/greptimedb/issues/602

Issue description:

Add system tables for inner metrics. It's good to have a metrics table like the one in Databend or ClickHouse. Users can easily "select" on the metrics table to see DB's important running status. With the metrics table, we can integrate other visualization tools or dashboards that support SQL like Grafana, to export some meaningful time series data.

  1. In datanode, create a new table called metrics, with a schema including at least metric, value, and description, and also feel free to add other columns when necessary. Register it into the default catalog as our ScriptsTable does.
  2. Implement "select" for the metrics table. Instead of actually storing the metrics, call the render() method of PROMETHEUS_HANDLE, and parse the result (Prometheus lines) as table output.
  3. In frontend, create the same metrics table as well. Unlike DistTable, the metrics table does not do distributed queries.

Highlights of Recent PR โ€‹

What's cooking on DB's develop branch โ€‹

#694

Remove the gRPC invocations between frontend and datanode in standalone mode. This avoids unnecessary network transfers and serialization/deserialization of data in standalone mode, reducing the overhead of frontend calls to the datanode. (Contributor: MichaelScofield)

#641

MySQL and PostgreSQL can use the same port for both plain-text connections and secure ones. Unlike http or gRPC transports, database protocols have their own TLS handshake process. So we might not be able to utilize haproxy or cloud load balancer for TLS termination. We have to implement Tls support in the database. (Contributor: SSebo)

#656

GreptimeDB is using OpenDAL as the object storage service, so theoretically, S3 storage should be a piece of cake. (Contributor: killme2008)

#558

GreptimeDB now supports syntax like DESC[RIBE] TABLE <name>; to describe the structure of a table, as well as the default values. (Contributor: morigs)

New things โ€‹

Recent Blog Recommendations โ€‹

Have a Grep Time, Making the Most of 2023 - GreptimeDB Roadmap for Next Year | Greptime Blog

This roadmap presents goals our team is working on and concepts we have for our shared community. It gives people a sense of what to expect in GreptimeDB over the next 6 months. Furthermore, it helps provide "starting points" for how to get involved, and a sense of what kind of projects we are looking for.

This Time, for Real: GreptimeDB is now open source | Greptime Blog

This is the very first article that says hello to the world for us. Learn how and why we built Greptime and try creating on your own.

Join our community

Get the latest updates and discuss with other users.

Subscribe to our newsletter

Get the latest dates and news about GreptimeDB.