Uh oh!
There was an error while loading. Please reload this page.
[feature](index change)Support light index change for ngram bf index - #48461
Merged
Conversation
hello-stephen
commented
Feb 28, 2025
Contributor
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
qidaye
commented
Feb 28, 2025
ContributorAuthor
run buildall |
qidaye
commented
Feb 28, 2025
ContributorAuthor
run compile |
qidayeforce-pushed
the
light_index_change_in_cloud
branch
from
March 3, 2025 03:13
679e17b to
d54f726Compareqidaye
commented
Mar 3, 2025
ContributorAuthor
run buildall |
2 similar comments
qidaye
commented
Mar 3, 2025
ContributorAuthor
run buildall |
qidaye
commented
Mar 3, 2025
ContributorAuthor
run buildall |
qidayeforce-pushed
the
light_index_change_in_cloud
branch
from
March 3, 2025 13:38
d54f726 to
6091a62Compareqidaye
commented
Mar 3, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Mar 3, 2025
TPC-H: Total hot run time: 31476 ms |
doris-robot
commented
Mar 3, 2025
TPC-DS: Total hot run time: 191500 ms |
doris-robot
commented
Mar 3, 2025
ClickBench: Total hot run time: 30.62 s |
qidayeforce-pushed
the
light_index_change_in_cloud
branch
from
March 5, 2025 12:56
6091a62 to
7d08604Compareqidaye
commented
Mar 5, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Mar 5, 2025
TPC-H: Total hot run time: 32307 ms |
doris-robot
commented
Mar 5, 2025
TPC-DS: Total hot run time: 185622 ms |
doris-robot
commented
Mar 5, 2025
ClickBench: Total hot run time: 30.68 s |
qidayeforce-pushed
the
light_index_change_in_cloud
branch
from
March 5, 2025 14:21
7d08604 to
4ede4efCompareqidaye
commented
Mar 5, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Mar 5, 2025
TPC-H: Total hot run time: 32126 ms |
doris-robot
commented
Mar 5, 2025
TPC-DS: Total hot run time: 192143 ms |
doris-robot
commented
Mar 5, 2025
ClickBench: Total hot run time: 31.1 s |
qidayeforce-pushed
the
light_index_change_in_cloud
branch
from
March 6, 2025 02:44
4ede4ef to
f25084aCompareqidaye
commented
Mar 6, 2025
ContributorAuthor
run buildall |
qidayeforce-pushed
the
light_index_change_in_cloud
branch
from
March 6, 2025 03:18
f25084a to
8723c95Compareqidaye
commented
Mar 6, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Mar 6, 2025
TPC-H: Total hot run time: 32896 ms |
doris-robot
commented
Mar 6, 2025
TPC-DS: Total hot run time: 185891 ms |
doris-robot
commented
Mar 6, 2025
ClickBench: Total hot run time: 31.13 s |
qidayeforce-pushed
the
light_index_change_in_cloud
branch
from
March 6, 2025 07:25
8723c95 to
6a7dbbfCompareairborne12force-pushed
the
light_index_change_in_cloud
branch
from
May 7, 2025 06:21
283baf0 to
0211cddCompareairborne12
commented
May 7, 2025
Member
run buildall |
doris-robot
commented
May 7, 2025
TPC-H: Total hot run time: 33875 ms |
doris-robot
commented
May 7, 2025
TPC-DS: Total hot run time: 192363 ms |
doris-robot
commented
May 7, 2025
ClickBench: Total hot run time: 28.98 s |
Contributor
PR approved by at least one committer and no changes requested. |
Contributor
PR approved by anyone and no changes requested. |
koarz pushed a commit
to koarz/doris
that referenced
this pull request
Jun 4, 2025
…pache#48461) ### What problem does this PR solve? Currently, NGram bloom filter index only supports directly schema change, and users need to build indexes incrementally when using it. The design goal is that ngrambf supports light_index_change, including local and cloud mode, which can incrementally add indexes or build indexes on stock data. Inverted indexes are currently only supported in local mode for light_schema_change, cloud mode is still a directly SC, this time it does not involve inverted indexes, and its functionality remains unchanged. After the completion of the function, the NGram BF index construction can be used in the following way, following the existing syntax, does not involve changes or additions. ```sql # add new index alter table t1 add index idx_ngram_k2 (`k2`) using ngram_bf properties("bf_size" = "1024", "gram_size" = "3"); create index idx_ngram_k2 (`k2`) on t1 using ngram_bf properties("bf_size" = "1024", "gram_size" = "3"); # build index on stock data build index idx_ngram_k2 on t1; # show build ngram index show alter table column; # cancel build index cancel build index on t1; ``` **NOTE:** Currently, building an index by partition is not supported. If you want to build an index for stock data, you need to build it for all data, including new data written after the Add index has been added. Build index by partition will be supported in next stage. ### Release note Support light index change for NGram bf index
airborne12 pushed a commit
to airborne12/apache-doris
that referenced
this pull request
Jul 7, 2025
…pache#48461) Currently, NGram bloom filter index only supports directly schema change, and users need to build indexes incrementally when using it. The design goal is that ngrambf supports light_index_change, including local and cloud mode, which can incrementally add indexes or build indexes on stock data. Inverted indexes are currently only supported in local mode for light_schema_change, cloud mode is still a directly SC, this time it does not involve inverted indexes, and its functionality remains unchanged. After the completion of the function, the NGram BF index construction can be used in the following way, following the existing syntax, does not involve changes or additions. ```sql alter table t1 add index idx_ngram_k2 (`k2`) using ngram_bf properties("bf_size" = "1024", "gram_size" = "3"); create index idx_ngram_k2 (`k2`) on t1 using ngram_bf properties("bf_size" = "1024", "gram_size" = "3"); build index idx_ngram_k2 on t1; show alter table column; cancel build index on t1; ``` **NOTE:** Currently, building an index by partition is not supported. If you want to build an index for stock data, you need to build it for all data, including new data written after the Add index has been added. Build index by partition will be supported in next stage. Support light index change for NGram bf index
airborne12 pushed a commit
to airborne12/apache-doris
that referenced
this pull request
Jul 9, 2025
…pache#48461) Currently, NGram bloom filter index only supports directly schema change, and users need to build indexes incrementally when using it. The design goal is that ngrambf supports light_index_change, including local and cloud mode, which can incrementally add indexes or build indexes on stock data. Inverted indexes are currently only supported in local mode for light_schema_change, cloud mode is still a directly SC, this time it does not involve inverted indexes, and its functionality remains unchanged. After the completion of the function, the NGram BF index construction can be used in the following way, following the existing syntax, does not involve changes or additions. ```sql alter table t1 add index idx_ngram_k2 (`k2`) using ngram_bf properties("bf_size" = "1024", "gram_size" = "3"); create index idx_ngram_k2 (`k2`) on t1 using ngram_bf properties("bf_size" = "1024", "gram_size" = "3"); build index idx_ngram_k2 on t1; show alter table column; cancel build index on t1; ``` **NOTE:** Currently, building an index by partition is not supported. If you want to build an index for stock data, you need to build it for all data, including new data written after the Add index has been added. Build index by partition will be supported in next stage. Support light index change for NGram bf index
morrySnow pushed a commit
that referenced
this pull request
Jul 9, 2025
airborne12 added a commit
to airborne12/apache-doris
that referenced
this pull request
Jul 9, 2025
…x without parser and ngram bf index apache#48461apache#52251 (apache#52894) cherry pick from apache#48461 and apache#52251 --------- Co-authored-by: qiye <jianliang5669@gmail.com>
16 tasks
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What problem does this PR solve?
Currently, NGram bloom filter index only supports directly schema change, and users need to build indexes incrementally when using it.
The design goal is that ngrambf supports light_index_change, including local and cloud mode, which can incrementally add indexes or build indexes on stock data.
Inverted indexes are currently only supported in local mode for light_schema_change, cloud mode is still a directly SC, this time it does not involve inverted indexes, and its functionality remains unchanged.
After the completion of the function, the NGram BF index construction can be used in the following way, following the existing syntax, does not involve changes or additions.
NOTE: Currently, building an index by partition is not supported. If you want to build an index for stock data, you need to build it for all data, including new data written after the Add index has been added.
Build index by partition will be supported in next stage.
Release note
Support light index change for NGram bf index
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)