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
Commit d1070cb
Browse filesBrowse the repository at this point in the historyBrowse files
[fix](fe) block inverted index V1 creation in FE (#64522)
### What problem does this PR solve?
Problem Summary:
When users copy historical DDL statements that explicitly set inverted
index format to V1, new tables are silently created with V1. Inverted
index V1 does not support small file merging and bypasses the packed
file path, significantly amplifying PUT requests to object storage.
Observed impact: clusters with high write QPS are seeing300–400 PUT/s,
with 70–80% attributed to inverted index V1.
Block new inverted index V1 creation at the FE level:
- Explicitly specifying `inverted_index_storage_format = v1` on a new
indexnow returns an error immediately.
- Users are guided to use V2 (the default).
- Existing V1 tables remain fully compatible — metadata loading and
read/write
are unaffected. No forced migration.
Error message:Inverted index V1 is deprecated and no longer allowed for
new index creation.Please use inverted index V2.
Coverage
- `CREATE TABLE` with inline index definition
- `ALTER TABLE ADD INDEX`
- All other code paths that create a new inverted index
### Release note
0 commit comments