Skip to content

Releases: GreptimeTeam/greptimedb

Release list

Release v1.1.3

Release v1.1.3

Choose a tag to compare

View all tags
@WenyXu WenyXu released this 17 Jul 03:46
v1.1.3
63ef18a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v1.1.3

Release date: July 17, 2026

GreptimeDB v1.1.3 is a patch release for the v1.1 line. It improves query correctness,
storage stability, and the bundled dashboard.

We recommend users on earlier v1.1 releases upgrade to v1.1.3.

👍 Highlights

  • Scalar-subquery rewrites preserve global ordering for ORDER BY ... DESC LIMIT 1 branches, avoiding a region-local latest row when the branch becomes an intermediate join input.
  • PromQL range and instant selectors can now push cast-based time filters to datanodes for metric tables using TIMESTAMP(6) or TIMESTAMP(9), improving scan pruning.

Dashboard

  • The embedded GreptimeDB dashboard was updated to v0.13.7. Table views are easier to resize
    and inspect, and the support menu is more prominent.
  • Dashboard snapshots can now capture the current time range, variable values, and panel query
    results in a self-contained, read-only dashboard that can be saved, exported, and opened
    without querying live data sources.

🚀 Features

🐛 Bug Fixes

All Contributors

We would like to thank the following contributors from the GreptimeDB community:

@WenyXu, @discord9, @fengjiachun, @sunchanglong, @sunng87, @v0y4g3r

Loading

Release v1.1.2-0783225e0-20260710-1783671342

Release v1.1.2-0783225e0-20260710-1783671342 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 10 Jul 09:23
v1.1.2-0783225e0-20260710-1783671342
03b3045
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's Changed

New Contributors

Full Changelog: v1.2.0-nightly-20260706...v1.1.2-0783225e0-20260710-1783671342

Contributors

sunng87, MichaelScofield, and 10 other contributors
Loading

Release v1.2.0-nightly-20260706

Release v1.2.0-nightly-20260706 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 06 Jul 02:57
v1.2.0-nightly-20260706
3758911
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's Changed

New Contributors

Full Changelog: v1.2.0-8513d8d6b-20260625-1782368704...v1.2.0-nightly-20260706

Contributors

killme2008, sunng87, and 11 other contributors
Loading

Release v1.1.2

Release v1.1.2

Choose a tag to compare

View all tags
@WenyXu WenyXu released this 02 Jul 13:58
v1.1.2
8ad2d24
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v1.1.2

Release date: July 02, 2026

GreptimeDB v1.1.2 is a patch release for the v1.1 line. It fixes scheduled Flow runtime semantics, improves slow-query context, and refreshes the bundled dashboards.

We recommend users on v1.1.0 and v1.1.1 upgrade to v1.1.2.

👍 Highlights

Scheduled Flow execution now uses stable logical time. Flows with EVAL INTERVAL now bind now() and current_timestamp() to the scheduled runtime, including distributed plans. This keeps scheduled windows stable instead of depending on when a worker happens to plan the query.

CREATE TABLE flow_input (
  ts TIMESTAMP(3) TIME INDEX,
  v DOUBLE,
  PRIMARY KEY(v)
);

CREATE FLOW flow_eval
SINK TO flow_eval_sink
EVAL INTERVAL '1s'
AS
SELECT
  date_bin(INTERVAL '1 second', ts) AS window_start,
  count(v) AS value_count,
  now() AS scheduled_at
FROM flow_input
WHERE ts >= date_trunc('second', now()) - INTERVAL '1 second'
  AND ts <  date_trunc('second', current_timestamp())
GROUP BY date_bin(INTERVAL '1 second', ts);

Slow query records include schema context. Slow query entries now carry the schema name for SQL, logical plan, and PromQL slow-query paths. This makes it easier to find which tenant or workload produced a slow query when multiple schemas share a cluster.

USE greptime_private;

SELECT schema_name, cost, threshold, query, timestamp
FROM slow_queries
ORDER BY timestamp DESC
LIMIT 10;

Dashboard

  • Bundled Grafana metrics dashboards were reorganized for cluster and standalone deployments. The update fixes histogram bucket queries and counter-rate normalization, separates latency panels, and collapses flush/compaction sections to make troubleshooting easier.
  • The embedded GreptimeDB dashboard was updated to v0.13.6. This dashboard release refines metric views and fixes SQL execution from the editor when the cursor is after a SQL line.

🚀 Features

🐛 Bug Fixes

⚡ Performance

⚙️ Miscellaneous Tasks

New Contributors

All Contributors

We would like to thank the following contributors from the GreptimeDB community:

@discord9, @evenyag, @fengjiachun, @RitwijParmar, @shuiyisong, @sunchanglong, @v0y4g3r, @WenyXu

Loading

Release v1.2.0-8513d8d6b-20260625-1782368704

Release v1.2.0-8513d8d6b-20260625-1782368704 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 25 Jun 07:30
v1.2.0-8513d8d6b-20260625-1782368704
9b16723
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's Changed

Full Changelog: v1.1.0-nightly-20260622...v1.2.0-8513d8d6b-20260625-1782368704

Contributors

killme2008, sunng87, and 5 other contributors
Loading

Release v1.1.0-nightly-20260622

Release v1.1.0-nightly-20260622 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 22 Jun 03:13
v1.1.0-nightly-20260622
b365e0d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's Changed

Full Changelog: v1.1.0...v1.1.0-nightly-20260622

Contributors

MichaelScofield, fengjiachun, and 6 other contributors
Loading

Release v1.1.1

Release v1.1.1

Choose a tag to compare

View all tags
@evenyag evenyag released this 18 Jun 09:48
v1.1.1
126c212
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v1.1.1

Release date: June 18, 2026

This release fixes a critical JSON compatibility bug that affects users upgrading from v1.0.x to v1.1.0, where legacy JSONB columns could return incorrect query results or fail during flush. It also removes a lock in the create flow procedure that could self-block sink table creation.

We strongly recommend users on v1.1.0 who use the JSON data type upgrade to v1.1.1.

🐛 Bug Fixes

  • fix: guard structured JSON alignment paths against legacy JSONB columns by @evenyag in #8323
  • fix: remove flow sink table lock by @discord9 in #8317

All Contributors

We would like to thank the following contributors from the GreptimeDB community:

@discord9, @evenyag

Loading

Release v1.1.0-nightly-20260615

Release v1.1.0-nightly-20260615 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 15 Jun 03:17
v1.1.0-nightly-20260615
c9062fe
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's Changed

Read more

Contributors

killme2008, sunng87, and 15 other contributors
Loading

Release v1.1.0

Release v1.1.0 Pre-release
Pre-release

Choose a tag to compare

View all tags
@evenyag evenyag released this 14 Jun 09:30
v1.1.0
c9062fe
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v1.1.0

Release date: June 14, 2026

v1.1.0 adds online partitioning for previously unpartitioned tables, experimental incremental
reads for batching flows, the experimental table semantic layer, and new CSV import options,
along with performance and stability fixes.

Warning

v1.1.0 contains a critical JSON compatibility bug that affects users upgrading from v1.0.x when using the JSON data type. We strongly recommend users on v1.1.0 who use the JSON data type upgrade to v1.1.1 or later.

👍 Highlights

Partition an existing table.

Previously only tables created with PARTITION ON COLUMNS
could be repartitioned, via SPLIT PARTITION and MERGE PARTITION. v1.1.0 supports
partitioning a table that has no partition rules, splitting its single region into multiple
partitions with ALTER TABLE ... PARTITION ON COLUMNS:

ALTER TABLE sensor_readings PARTITION ON COLUMNS (device_id, area) (
  device_id < 100 AND area < 'South',
  device_id < 100 AND area >= 'South',
  device_id >= 100 AND area <= 'East',
  device_id >= 100 AND area > 'East'
);

The layout can then be adjusted further with SPLIT PARTITION and MERGE PARTITION.
Repartitioning requires a distributed cluster with shared object storage and GC enabled.

Experimental incremental read for flows

Batching flows re-execute the full source query
on every evaluation. With incremental read enabled, a flow only reads source rows appended
since its last run, lowering overhead for large append-only sources. It is disabled by
default; enable it in the flownode config:

[flow.batching_mode]
experimental_enable_incremental_read = true

It can also be set per flow with WITH (experimental_enable_incremental_read = 'true'). The
source table must be append-only (append_mode = 'true'); otherwise the flow falls back to
full-snapshot queries.

Table semantic layer

The experimental table semantic layer lets tables carry
greptime.semantic.* metadata, such as signal type, source, metric type, unit, temporality,
and ingestion pipeline. GreptimeDB stamps this metadata automatically on supported ingestion
paths, and you can also set it manually with CREATE TABLE ... WITH (...). Consumers can
query information_schema.table_semantics to understand what each table represents without
guessing from table or column names.

MCP Server v0.5.0

GreptimeDB MCP Server v0.5.0 uses table semantic metadata in describe_table, so AI
assistants can understand metrics, logs, and traces more directly. It also expands the tool
set for SQL, TQL, RANGE queries, pipelines, and dashboards, with stdio/SSE/Streamable HTTP
transports, read-only defaults, masking, and audit logging.

Query performance improvements

  • PromQL execution. Range functions such as rate and increase run faster, with
    benchmarks showing up to 97% lower execution time. Metric joins also improve through
    TSID-based joins and narrow binary join collection. Overall, compared to v1.0, v1.1 reduces
    average PromQL query time by 20% to 40%.
  • Scan pruning. Parquet prefiltering, prefilter-result caching, and remote dynamic
    filters on datanode scans reduce unnecessary row reads. The TSBS cpu-max-all-8 query was
    4.5x faster with prefiltering.
  • Read efficiency. Page-index reads and range-cache reuse reduce storage reads for
    scan-heavy queries. Page-index reads reduced SST bytes fetched by 93.2% on one workload.

Dashboard

  • The built-in Perses dashboard now supports trace visualization: a trace list and a
    per-trace detail/Gantt view from the trace table, using the GreptimeDB Perses data-source
    plugin.

CSV import options

COPY FROM adds SKIP_BAD_RECORDS = 'true' for skipping invalid rows and HEADERS = 'false'
for importing headerless CSV files:

COPY tbl FROM '/path/to/file.csv' WITH (
  FORMAT = 'csv',
  SKIP_BAD_RECORDS = 'true',
  HEADERS = 'false'
);

Breaking changes

🚀 Features

Read more
Loading

Release v1.1.0-nightly-20260525

Release v1.1.0-nightly-20260525 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 25 May 03:25
v1.1.0-nightly-20260525
8c267f3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's Changed

Full Changelog: v1.0.0-nightly-20260518...v1.1.0-nightly-20260525

Contributors

MichaelScofield, fengjiachun, and 8 other contributors
Loading