What GreptimeTeam/greptimedb shipped
Generated by FoxPlug from public activity — not affiliated with Greptime.
Week of September 14, 2026
What shipped
- Trace V2 ingestion now available with JSON2 attributes for span, scope, and resource data. Pull request #9192
- Jaeger queries now supported for Trace V2 with optimized writes. Pull request #9257
- HTTP protocol now batches ordinary table writes for improved efficiency. Pull request #9115
- Two-phase series scans now use series and range indexes to improve performance. Pull request #9153
- Range index reads and builds made opt-in via experimental_enable_range_index flag. Pull request #9219
- Object store WAL log store now supports construction and recovery. Pull request #9238
- Region statistics now expose min and max timestamps. Pull request #9060
- PromQL binary operands now propagate matching-label filters for better filtering. Pull request #9202
- Prometheus remote read now merges duplicate timeseries across record batches. Pull request #9032
- Primary key range comparison across schema versions fixed in mito2 compaction. Pull request #9205
Why it matters
This week brings Trace V2 fully online with JSON storage and Jaeger query support, enabling better observability data handling. Performance work across PromQL, series scanning, and HTTP batching reduces resource usage. Infrastructure improvements to object store WAL and region statistics support future scaling.
Changelog entry
- feat(otlp): add trace v2 ingestion with JSON2 attributes Pull request #9192
- feat(trace): support Jaeger queries for Trace V2 and optimize writes Pull request #9257
- feat: batch ordinary table writes across HTTP protocols Pull request #9115
- perf(mito2): use series and range indexes in two-phase series scans Pull request #9153
- feat(mito2): make range index reads and builds opt-in Pull request #9219
- perf(promql): propagate matching-label filters between binary operands Pull request #9202
- fix(servers): merge duplicate timeseries across RecordBatches in Prometheus remote read Pull request #9032
- feat(log-store): add object store WAL store construction and recovery Pull request #9238
- feat: expose region min/max timestamp in region_statistics Pull request #9060
- feat(otlp): preserve trace v2 events and links as JSON Pull request #9232
- fix(mito2): compare primary key ranges across schema versions Pull request #9205
- feat(mito2): split SWCS output files by size threshold Pull request #9259
- perf(mito2): lazily materialize sparse primary key tags Pull request #9199
- perf(servers): reduce temporary memory in protocol handling Pull request #9249
- feat(json2): respect type hints during JSON2 type concretization Pull request #9222
- perf(otlp): share trace resource and scope attributes Pull request #9253
- feat: add status label to datanode failed-insert metric Pull request #9191
[36] Trace V2 ingestion is live with JSON2 attributes. [1] Jaeger queries now work with Trace V2. [37] HTTP writes batch ordinary tables. Performance optimizations in PromQL, series scans, and mito2.
This week's GreptimeDB release brings Trace V2 to production with full JSON attribute support and Jaeger query compatibility [36][1]. We optimized HTTP write batching for ordinary tables [37], improved PromQL filter propagation [22], and enhanced two-phase series scans with index usage [39]. Object store WAL infrastructure for log stores is now complete [17], and region statistics now expose timestamp bounds [16]. Configuration flexibility improved with opt-in range index support [9].