Summary
June 2026 · 2026-06-01 – 2026-06-30
Starting this issue (No. 85), the report switches from a biweekly to a monthly cadence.
What landed this month:
- Remote dynamic filters now push predicates down to datanode scans at query time.
- Optimizer rules now run before
MergeScanwraps the remote plan, so filters reach datanode scans for pruning. - JSON columns accept type hints to control how values are parsed and stored.
GreptimeDB also shipped v1.1.1 this month. Still on an older version? Upgrade to the latest release.
Contributors
Over the past month, 22 contributors merged a total of 131 PRs. Among them, 8 individual contributors contributed 10 PRs. Welcome to our new contributors: @raphaelroshan, @agrawalx, @RitwijParmar!
Thanks to the community contributors who shipped this month:
Highlights
db#8298 fix: improve Grafana metrics dashboards
The Grafana dashboards for cluster and standalone deployments now have corrected panel queries for histogram buckets and counter rate normalization, fixed datasource references in trigger panels, and separated request latency panels into distinct views for easier troubleshooting.
db#8247 feat(json2): type hint
JSON2 columns now accept type hints at table creation time, letting you declare paths like "user"."age" BIGINT NOT NULL DEFAULT 18 directly in the column definition. Writes to JSON2 columns respect these declared types and defaults.
db#8262 & db#8148 feat: remote dynamic filters, end to end
Remote Dynamic Filters (RDF) now work across nodes. On the frontend, query planning assigns stable FilterId values to MergeScan producers and dispatches initial registration records to datanodes (db#8148). At execution time, eligible predicates—such as those produced by hash joins—are pushed down to RegionScanExec on the datanode (db#8262), so datanodes can prune data earlier without waiting for the full query plan to complete.
db#8339 fix(query): run optimizer rules before MergeScan
Filters on distributed queries with LEFT JOIN or subqueries previously could not reach remote TableScan.filters because MergeScan hides the remote plan from DataFusion's optimizer. A targeted optimizer prepass now runs PushDownFilter and related rules before MergeScan wraps the remote input, so scan predicates reach datanodes for region pruning.
Ecosystem Updates
TypeScript Ingester
2 releases this month (v0.2.1, v0.2.0).
- Multi-endpoint failover via a pluggable
EndpointSelectorinterface. Decimal128is now supported for write operations.- Client-side timeouts no longer trigger unnecessary endpoint retries or ejections.
.NET Ingester
1 release this month (v0.2.1).
GreptimeClientOptions.Failoveradds request-level retry across endpoints for unary writes and deletes.- Failed endpoints are ejected with exponential backoff and reinstated automatically via
FailoverOptionstunables. GreptimeServerExceptionsurfaces the server status code so callers can distinguish retryable from terminal errors.
Dashboard
3 releases this month (v0.13.6, v0.13.1, v0.13.0).
- Configuration handling was refactored—connection settings and UI preferences are now persisted separately for more reliable state.
- A new dark theme is available for the main UI.
- Metric view visuals were refreshed, plus a fix for selecting SQL when the cursor sits after a SQL line.
MCP Server
2 releases this month (v0.5.1, v0.5.0).
- Prompts now use sandboxed Jinja rendering for safer template evaluation.
describe_tablenow returns a richer table profile—semantic metadata, latest sample rows, query guidance, and column comments—so AI agents get the full picture in one call.explain_querygains an opt-in verbose mode that exposes scan-level metrics.
Good First Issues
New to GreptimeDB? These are scoped for a first contribution. Comment on an issue to pick it up.
Issue#7314 Feature Request: Add built-in daemon mode to keep GreptimeDB running independently of shell sessions
Add a --daemon (or -d) CLI flag to GreptimeDB's standalone mode so the process detaches from the shell session and runs in the background, including PID management and stdout/stderr redirection.
Keywords: CLI, Daemon/Process Management
Difficulty: Medium
Issue#7987 feat: add flow_statistics system table and SHOW FLOW STATUS for flow runtime observability
Add a flow_statistics system table and a SHOW FLOW STATUS SQL command that expose per-flow runtime data such as start time, uptime, processed data volume, and recent errors.
Keywords: SQL, Observability, System Tables
Difficulty: Medium
Get Involved
- Docs: https://docs.greptime.com
- GitHub: https://github.com/GreptimeTeam/greptimedb
- X: https://x.com/Greptime
Questions, bug reports, or feature ideas are all welcome. Open an issue or say hi in the community channel.


