Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update changelog #862

Merged
merged 12 commits into from
Apr 3, 2024
Binary file added docs/public/version-plan1.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

This file was deleted.

5 changes: 0 additions & 5 deletions docs/v0.7/en/changelog/biweekly-reports/overview.md

This file was deleted.

31 changes: 31 additions & 0 deletions docs/v0.7/en/changelog/historical-releases/version-0-7-0.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# v0.7.0

Release date: March 12, 2024

This is a major version update, read [this Blog](https://www.greptime.com/blogs/2024-03-07-greptimedb-v0.7) to learn more detail about the feature and performance updates.

v0.7 represents a crucial leap toward achieving production readiness; it implements production-ready features for cloud-native monitoring scenarios.

**Highlights**

- Metric Engine: handles a large number of small tables, making it particularly suitable for cloud-native monitoring.

- Region Migration: enhances the user experience and simplifies region migrations with straightforward SQL commands.

- Inverted Index: dramatically improves the efficiency of locating data segments relevant to user queries, significantly reducing the IO operations needed for scanning data files and thus accelerating the query process.

## Feature Updates

- Region Migration
- Metric Engine

## Performance Improvement

## Bug Fixes

## Contributors

We would like to thank the following contributors from the GreptimeDB community:
- AA
- BB
- CC
3 changes: 0 additions & 3 deletions docs/v0.7/en/changelog/overview.md

This file was deleted.

107 changes: 107 additions & 0 deletions docs/v0.7/en/changelog/roadmap.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,107 @@
# What to Expect Next? GreptimeDB Roadmap for 2024

Since GreptimeDB's open-sourcing on November 15th, 2022, we have stepped on the committed journey towards crafting a fast and efficient data infrastructure. This endeavor has been propelled by the collaborative efforts of both our dedicated team and the vibrant community that supports us.

As we embark on the inaugural season of 2024, a leap year enriched by an extra day in February, this year promises to be thrilling as we anticipate numerous groundbreaking developments. These crucial updates will significantly showcase the maturity of our product within production environments, presenting practical benchmarks for users to compare with leading time-series databases in the industry.

As we forge ahead with GreptimeDB 2024, it prompts the question, "What's next?" This roadmap outlines the objectives our team is pursuing and the visions we harbor for our collective community.

- Providing clarity on what the community can expect from GreptimeDB for the next 10-12 months;
- Offering insights to those wishing to contribute to GreptimeDB on GitHub by highlighting potential starting points and the types of projects we are eager to embark on.

Read the updated roadmap in [this issue](https://github.com/GreptimeTeam/greptimedb/issues/3412).

## Main Feature Updates in 2024

The evolution of GreptimeDB in 2024 is marked by a suite of main feature updates. These enhancements are a testament to our ongoing commitment to excellence, driven by feedback from our community and the latest requirements in real-world scenarios.

Our roadmap for the year includes significant advancements that promise to elevate the capabilities of GreptimeDB and enrich the user experience.

Here's a glimpse into what we have in store:

- [Metric Engine](https://github.com/GreptimeTeam/greptimedb/blob/main/docs/rfcs/2023-07-10-metric-engine.md)

- Tracking issue: https://github.com/GreptimeTeam/greptimedb/issues/3187

- A new engine designed for observability scenarios. Its primary aim is to handle a large number of small tables, making it particularly suitable using Prometheus metrics. By utilizing synthetic wide tables, this new Engine offers the capability to store metric data and reuse metadata, rendering "tables" atop it more lightweight and overcoming some of the limitations of the existing Mito engine, which is considered too heavy for such tasks.

- [GreptimeFlow](https://github.com/GreptimeTeam/greptimedb/blob/main/docs/rfcs/2024-01-17-dataflow-framework.md)

- Tracking issue: https://github.com/GreptimeTeam/greptimedb/issues/3187
- A lightweight stream computing component capable of performing continuous aggregation on GreptimeDB data streams. It can be embedded into the GreptimeDB Frontend or deployed as a separate service within the GreptimeDB cluster.
- A flow job can be submitted in the form of SQL:

```sql
CREATE TASK avg_over_5m WINDOW_SIZE = "5m" AS
SELECT avg(value) FROM table
WHERE time > now() - 5m GROUP BY time(1m);
```

- Index
- [Inverted Index](https://github.com/GreptimeTeam/greptimedb/blob/main/docs/rfcs/2023-11-03-inverted-index.md)
- Tracking issue: https://github.com/GreptimeTeam/greptimedb/issues/2705
- Smart Index
- For instance, it automatically monitors workloads and query performance, and when necessary, it autonomously creates relevant indexes and removes unused ones.
- Spatial Index
- Supports storage and retrieval of geographic location information.

- Cluster Management & Autopilot
- [Region Migration](https://github.com/GreptimeTeam/greptimedb/blob/main/docs/rfcs/2023-11-07-region-migration.md)
- Tracking issue: https://github.com/GreptimeTeam/greptimedb/issues/2700
- It offers the capability to migrate Regions between Datanodes, facilitating the relocation of hot data and the horizontal scaling of load balancing.
- Auto Rebalance Regions
- An automated load balancing scheduler built upon Region Migration.

- Logs Engine
- A storage engine designed specifically for the characteristics of log data, sharing most of GreptimeDB's architecture and capabilities, such as the SQL query layer, data sharding, distributed routing, and querying indexing, and compression ability. This enables GreptimeDB to become a unified system offering optimized storage and a consistent access experience for both Metrics and Logs data, based on a multi-engine architecture.


## GreptimeDB Version Plan

With all the feature updates listed above, we've made the version iteration plan for GreptimeDB in 2024.

The image below presents the GreptimeDB 2024 Roadmap, showcasing a structured release schedule and the pivotal feature enhancements planned for deployment throughout the year. Please note that these details are tentative and subject to refinement.

![version iteration plan](/version-plan1.png)

Track the progress of GreptimeDB versions [here](https://github.com/GreptimeTeam/greptimedb/milestones).

GreptimeDB v1.0 marks a milestone as a production-ready release, boasting advanced features such as Smart Index, setting a new standard for efficiency and performance.

Here we enthusiastically invite you to mark your calendar and experience the robust capabilities of GreptimeDB v1.0 (scheduled to be released in August) to boost your time-series data management and analysis.

**March: GreptimeDB v0.7**

- Region Migration
- Inverted Index
- Metrics Engine

**April: GreptimeDB v0.8**

- GreptimeFlow

**June: GreptimeDB v0.9**

- Auto Rebalance Regions

**August: GreptimeDB v1.0**

- Smart Index
- Spatial Index

**December: GreptimeDB v1.1**

- Logs Engine: Data ingestion from popular log collectors


## Get Involved Now

If anything above draws your attention, don't hesitate to star us on [GitHub](https://github.com/GreptimeTeam/greptimedb) or GreptimeDB Community on [Slack](https://www.greptime.com/slack). Also, you can go to our [contribution page](https://github.com/GreptimeTeam/greptimedb/contribute) to find some interesting issues to start with.

Looking beyond the initiatives that are in progress, there's a lot of room for improvement. We also welcome other ideas besides these planned updates. If you might be interested in giving that a try, speak up and chat with the team. We probably will end up being the ones who get you the best.

---

To learn about our previous roadmaps, kindly refere to the blog posts below:

- [2023 Roadmap](https://www.greptime.com/blogs/2022-11-29-have-a-grep-time-making-the-most-of-2023): Have a Grep Time, Making the Most of 2023 - GreptimeDB Roadmap for Next Year
7 changes: 3 additions & 4 deletions docs/v0.7/en/summary.yml
Original file line number Diff line number Diff line change
Expand Up @@ -183,10 +183,9 @@
- how-to-use-tokio-console
- how-to-trace-greptimedb
- Changelog:
- overview
- Biweekly-Reports:
- overview
- latest-biweekly-report
- roadmap
- Release-Log:
- version-0-7-0
- FAQ-and-Others:
- overview
- faq
Loading