fix: rebuild missing bloom index while pruning #15738
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
Fix missing bloom index during bloom pruning.
introduce new setting
enable_auto_fix_missing_bloom_index
which is false (disabled) by default.when it was enabled, missing bloom indexes detected during pruning will be created automatically. (only those bloom index that used by the query, will be rebuilt, not all of them).
this feature is intended to repair a small amount of missing bloom indexes. if a table's bloom indexes are largely lost, such as being mostly deleted by mistake, and subsequent queries are expected to encounter most of these missing bloom indexes, please be aware that rebuilding bloom indexes takes time and may significantly impact query performance.
Tests
Type of change
This change is