Skip to main content
Skip to main content

NGram BloomFilter Index

[Experimental] NGram BloomFilter Index

SinceVersion 2.0.0

In order to improve the like query performance, the NGram BloomFilter index was implemented.

Create Column with NGram BloomFilter Index

During create table:

CREATE TABLE `table3` (
`siteid` int(11) NULL DEFAULT "10" COMMENT "",
`citycode` smallint(6) NULL COMMENT "",
`username` varchar(100) NULL DEFAULT "" COMMENT "",
INDEX idx_ngrambf (`username`) USING NGRAM_BF PROPERTIES("gram_size"="3", "bf_size"="256") COMMENT 'username ngram_bf index'
AGGREGATE KEY(`siteid`, `citycode`, `username`) COMMENT "OLAP"
"replication_num" = "1"

-- PROPERTIES("gram_size"="3", "bf_size"="1024"),indicate the number of gram and bytes of bloom filter respectively.
-- the gram size set to same as the like query pattern string length. and the suitable bytes of bloom filter can be get by test, more larger more better, 256 maybe is a good start.
-- Usually, if the data's cardinality is small, you can increase the bytes of bloom filter to improve the efficiency.

Show NGram BloomFilter Index

show index from example_db.table3;

Drop NGram BloomFilter Index

alter table example_db.table3 drop index idx_ngrambf;

Add NGram BloomFilter Index

Add NGram BloomFilter Index for old column:

alter table example_db.table3 add index idx_ngrambf(username) using NGRAM_BF PROPERTIES("gram_size"="3", "bf_size"="512")comment 'username ngram_bf index' 

Some Notes about Doris NGram BloomFilter

  1. NGram BloomFilter only support CHAR/VARCHAR/String column.
  2. NGram BloomFilter index and BloomFilter index should be exclusive on same column
  3. The gram number and bytes of BloomFilter can be adjust and optimize. Like if gram is too small, you can increase the bytes of BloomFilter.
  4. To find some query whether use the NGram BloomFilter index, you can check the query profile.