GreptimeDB v1.2.0-beta.2 introduces breaking changes to soft-drop lifecycle and histogram schema

GreptimeDB v1.2.0-beta.2, released on August 21, 2026, brings several updates focused on table administration, observability, JSON2 preparation, and correctness fixes. Notable changes include the introduction of one-way skip_wal modifications via ALTER TABLE, enhanced JSON2 extension handling, and improved procedure event observability. However, this release also reintroduces enterprise-only gating for soft-drop table operations and modifies the schema for native histogram persisted fields.

According to the project's GitHub release notes, soft-drop and recovery operations, previously accessible in the OSS beta1 version, are now gated behind the enterprise feature in beta2. OSS users must remove the gc.experimental_soft_drop.enable setting before upgrading, as it will be rejected during startup. Additionally, tables soft-dropped in beta1 cannot be recovered or purged in beta2 unless using the Enterprise Edition. Operators should ensure any necessary tables are recovered prior to upgrading to avoid data loss.

Another breaking change involves the schema for native histogram persisted fields. The span-length list elements and count fields have shifted from unsigned to signed integers, with field names updated accordingly. Data written with the previous schema may become unreadable in beta2, and rolling back binaries does not restore compatibility. Operators must plan for migration or reingestion of affected data before upgrading, as mixed-version setups are unsupported.

These changes highlight the importance of reviewing compatibility and operational impacts when upgrading to beta releases, especially when schema alterations or feature gating are involved.