You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Validate partition expressions across all regions before ALTER #9454
Persisted partition bounds retain their original types when a column's type changes. A bound at 3000-01-01T00:00:00Z fits TIMESTAMP(3) but overflows TIMESTAMP(9), even if every stored row fits the new unit. The partition-filter coercion in #9418 returns an arithmetic overflow error during scan construction. Its regression test covers this path; it does not prevent ALTER from accepting incompatible partition bounds.
ALTER should validate partition-expression compatibility for all affected regions before changing any region. Validation only when each region applies ALTER can leave earlier regions modified when a later region rejects its bound.
Scope:
Validate persisted partition expressions against the proposed schema, including timestamp-unit widening and changes to nullable field columns referenced by partitions.
Reject incompatible changes before submitting ALTER to any region, without dropping partition predicates or converting overflowing bounds to NULL.
Cover a multi-region case where only a later region has an incompatible bound and assert that rejection leaves every region and the table schema unchanged.
Cover compatible changes and verify query results after ALTER.
The current regression test exercises scan construction directly. An end-to-end ALTER reproduction remains part of this follow-up.
Activity
fix(meta): validate persisted partition bounds before altering regions (
fix(meta): validate persisted partition bounds before altering regions (
fix(meta): validate persisted partition bounds before altering regions (
fix(meta): validate persisted partition bounds before altering regions (
fix: backport selected fixes to v1.3 (#10006)