Fix usage of non-materialized skip indexes#32359
Conversation
|
|
||
| INSERT INTO t_index_non_materialized VALUES (1); | ||
|
|
||
| ALTER TABLE t_index_non_materialized ADD INDEX ind (a) TYPE set(1) GRANULARITY 1; |
There was a problem hiding this comment.
Nice catch! Worth adding a check for minmax index too? (since it is a separate code branch)
There was a problem hiding this comment.
There already exists a check
ClickHouse/src/Storages/MergeTree/MergeTreeIndexMinMax.cpp
Lines 216 to 223 in 4e6bf24
Added it to test.
There was a problem hiding this comment.
There already exists a check
Yep, I meant adding it to test (since those branches can be modified independently)
|
Please help to backport this fix to 21.11. Thanks. |
|
@CurtizJ can this be merged? |
|
@Mergifyio update |
✅ Branch has been successfully updated |
|
There are failing tests. This PR will be merged after either author (@CurtizJ) or reviewer (@kitaisreal) will check and investigate the failures of the tests. If PR has failing tests, it cannot be merged as is. |
|
Stress test: |
Backport #32359 to 21.9: Fix usage of non-materialized skip indexes
Backport #32359 to 21.11: Fix usage of non-materialized skip indexes
Backport #32359 to 21.12: Fix usage of non-materialized skip indexes
Backport #32359 to 21.10: Fix usage of non-materialized skip indexes
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Fix failures in queries that are trying to use skipping indices, which are not materialized yet. Fixes #32292 and #30343.