# JSON Type Hints & Remote Dynamic Filter Pushdown | Greptime Monthly Report - No. 85

Source: https://greptime.com/blogs/2026-06-30-greptimedb-monthly-report

## 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 `MergeScan` wraps 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](https://github.com/GreptimeTeam/greptimedb/releases/tag/v1.1.1) this month. Still on an older version? [Upgrade to the latest release](https://github.com/GreptimeTeam/greptimedb/releases/latest).

## 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](https://github.com/raphaelroshan)**, **[@agrawalx](https://github.com/agrawalx)**, **[@RitwijParmar](https://github.com/RitwijParmar)**!

Thanks to the community contributors who shipped this month:

- **[@agrawalx](https://github.com/agrawalx)** *[db#8321](https://github.com/GreptimeTeam/greptimedb/pull/8321)*
- **[@QuakeWang](https://github.com/QuakeWang)** *[db#8233](https://github.com/GreptimeTeam/greptimedb/pull/8233)* *[db#8198](https://github.com/GreptimeTeam/greptimedb/pull/8198)*
- **[@lyang24](https://github.com/lyang24)** *[db#8254](https://github.com/GreptimeTeam/greptimedb/pull/8254)*

## Highlights

### [db#8298](https://github.com/GreptimeTeam/greptimedb/pull/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](https://github.com/GreptimeTeam/greptimedb/pull/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](https://github.com/GreptimeTeam/greptimedb/pull/8262) & [db#8148](https://github.com/GreptimeTeam/greptimedb/pull/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](https://github.com/GreptimeTeam/greptimedb/pull/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](https://github.com/GreptimeTeam/greptimedb-ingester-ts/releases/tag/v0.2.1), [v0.2.0](https://github.com/GreptimeTeam/greptimedb-ingester-ts/releases/tag/v0.2.0)).

- Multi-endpoint failover via a pluggable `EndpointSelector` interface.
- `Decimal128` is 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](https://github.com/GreptimeTeam/greptimedb-ingester-dotnet/releases/tag/v0.2.1)).

- `GreptimeClientOptions.Failover` adds request-level retry across endpoints for unary writes and deletes.
- Failed endpoints are ejected with exponential backoff and reinstated automatically via `FailoverOptions` tunables.
- `GreptimeServerException` surfaces the server status code so callers can distinguish retryable from terminal errors.

### Dashboard

3 releases this month ([v0.13.6](https://github.com/GreptimeTeam/dashboard/releases/tag/v0.13.6), [v0.13.1](https://github.com/GreptimeTeam/dashboard/releases/tag/v0.13.1), [v0.13.0](https://github.com/GreptimeTeam/dashboard/releases/tag/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](https://github.com/GreptimeTeam/greptimedb-mcp-server/releases/tag/v0.5.1), [v0.5.0](https://github.com/GreptimeTeam/greptimedb-mcp-server/releases/tag/v0.5.0)).

- Prompts now use sandboxed Jinja rendering for safer template evaluation.
- `describe_table` now returns a richer table profile—[semantic metadata](https://docs.greptime.com/user-guide/concepts/semantic-layer/), latest sample rows, query guidance, and column comments—so AI agents get the full picture in one call.
- `explain_query` gains 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](https://github.com/GreptimeTeam/greptimedb/issues/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](https://github.com/GreptimeTeam/greptimedb/issues/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.
