What GreptimeTeam/greptimedb shipped

This week in GreptimeDB: native raw PromQL runs over real datanodes, fulltext indexes on JSON paths, native histogram queries on the native PromQL route, fairer compaction scheduling across regions, and dashboard v0.14.3.

This week in GreptimeDB: native raw PromQL now executes over real datanodes, and native histograms can be queried through the same native route. Fulltext indexes are now supported on JSON paths. On storage, compaction units are scheduled fairly across regions and bulk memtable compaction shares one dispatcher across workers. The datanode drain admin endpoint accepts parallelism and strategy settings, frontend SQL requests can carry an optional timezone, and the bundled dashboard is updated to v0.14.3. Fixes include region ALTER priority over queued edits and decoding of cached manifest payloads on region reopen.

GreptimeDB v1.3.0 is out: native histogram ingestion, a semantic entity graph over metrics and traces, an opt-in trace schema with JSON2 attributes, and automatic retries for distributed writes. Also this week: a logfmt pipeline processor and InfluxDB line protocol ingest via COP

GreptimeDB v1.3.0 is released. It adds native histogram ingestion, a semantic entity graph over metrics and traces, an opt-in trace schema with JSON2 attributes, and automatic retries for distributed writes. The release also fixes incorrect SQL and PromQL results and write routing during scaling. Other changes this week: a built-in logfmt pipeline processor, InfluxDB line protocol ingest through PostgreSQL COPY FROM STDIN, object storage probing at datanode startup, and pipelined compaction that overlaps merge with encoding. Fixes cover memory and acknowledgement accounting in Prometheus remote write v2, preservation of live index files across remote compactions, and stale leader grants after a region downgrade.

This week: PromQL statements run through the fused native node in the production planner; complete aggregation over parallel partitions; histogram, topk and range modifier support; faster log-store recovery; safer SST retention; pipeline JSON column fixes.

This week in GreptimeDB: real PromQL statements now reach the fused native node and run through the production planner, starting with rate and nested expressions while unsupported shapes keep their existing plan. The native path also gained complete aggregation over parallel fused partitions, native histogram functions as map operations, topk and related operators in the vector node, and the anchored and smoothed range modifiers. Elsewhere, log-store recovery reads object store WAL footers while the recovery listing continues, mito2 keeps SSTs when a manifest save ends with RateLimited or PermissionDenied, pipelines accept auto-transformed arrays and objects into existing JSON columns, and region engine options can be overridden from environment variables.

This week: experimental_native_promql option, native instant PromQL over raw series, a scan-bound raw series surface, and log-store WAL work that no longer scales reclaim with region count.

This week in GreptimeDB: an experimental_native_promql option (off by default) plus native instant PromQL execution over raw series, with preflight and execution surfaces added across query traits, the datanode trait and region scanners. Log-store WAL work makes the object store reclaim boundary independent of region count and reuses release records during recovery. Failover can fall back on affinity, OTLP trace spans are chunked across resource groups, and columns can now choose an encoding, used for trace span ids.

This week: instant queries of range-vector expressions no longer crash, boolean OTLP metric attributes are kept as labels, TWCS windows were aligned, and object store WAL garbage collection landed.

This week in GreptimeDB: instant queries of range-vector expressions now return results instead of crashing, boolean OTLP metric attributes are converted into labels rather than dropped, and TWCS assignment now follows half-open time windows. On the storage side, the object store WAL gained garbage collection below a persisted reclaim boundary plus metrics and a conditional-create fault matrix. OTLP trace ingestion now caches service and operation writes, import-v2 batches logical table DDL, and nested MergeScan plans run on the datanode.

GreptimeDB v1.3.0-beta.1 is out with native histogram support, PromQL @ modifier, gRPC-Web CORS, HDFS storage, and WAL durability guarantees. Production release coming soon.

GreptimeDB v1.3.0-beta.1 brings major improvements for production deployments: native Prometheus histograms enabled by default, PromQL @ modifier for timestamp-based queries, CORS support for browser clients, HDFS storage backend, and WAL durability guarantees for cross-region recovery. The release focuses on Prometheus compatibility and infrastructure reliability.

This week: object store WAL chains, vector aggregate fixes, PromQL matching corrections, native histogram support enabled, and stable Rust 1.96.1. Several query correctness and performance improvements shipped.

This week's changes strengthen GreptimeDB's durability and query correctness. We implemented object store WAL chaining with recovery, fixed vector aggregate and PromQL vector matching issues, enabled native histogram ingestion by default, and switched to stable Rust toolchain. Performance improvements include lazy decoding of primary keys and better label filter pushing in PromQL joins.

Trace V2 ingestion is live with JSON2 attributes. Jaeger queries now work with Trace V2. 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. We optimized HTTP write batching for ordinary tables, improved PromQL filter propagation, and enhanced two-phase series scans with index usage. Object store WAL infrastructure for log stores is now complete, and region statistics now expose timestamp bounds. Configuration flexibility improved with opt-in range index support.