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
Core: TableMetadata.Builder allows adding encryption keys to v1/v2 tables #18632
encryption-keys is v3-only, but TableMetadata.Builder.addEncryptionKey doesn't check the format version. REST servers built on CatalogHandlers accept add-encryption-key from any client and write it into v1/v2 metadata.
Proposed fix
Reject in TableMetadata.Builder.addEncryptionKey below v3. This covers Java clients and REST servers, since both go through the builder. removeEncryptionKey and parsing should stay lenient so existing tables can be cleaned up.
Java's own writers don't check the version either (manifest list encryption), they rely on encryption.key-id being rejected on v1/v2 at create (#14668).
Activity
xanderbailey commentedon Oct 24, 2026
To me your analysis for this seems correct, I think we should be more strict about this