This is an automated email from the ASF dual-hosted git repository.

airborne pushed a change to branch auto-pick-43480-branch-3.0
in repository https://gitbox.apache.org/repos/asf/doris.git


 discard 8d5e311af2f [fix](ngram bloomfilter) fix narrow conversion for ngram 
bf_size (#43480)
     add 60f17d870ad branch-3.0: [fix] (bloom filter) Fix the bloom filter 
calculation for date and datetime (#43612)
     add b7358134e70 [fix] (inverted index) fix index compaction #43046 (#43614)
     add 56122c8440a [fix](ngram bloomfilter) fix narrow conversion for ngram 
bf_size (#43480)

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (8d5e311af2f)
            \
             N -- N -- N   refs/heads/auto-pick-43480-branch-3.0 (56122c8440a)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 be/src/olap/compaction.cpp                         |   1 -
 be/src/olap/comparison_predicate.h                 |  13 +-
 be/test/olap/date_bloom_filter_test.cpp            | 192 +++++++++++++++++++++
 .../test_index_compaction_empty_segments.groovy}   |  98 +++--------
 4 files changed, 227 insertions(+), 77 deletions(-)
 create mode 100644 be/test/olap/date_bloom_filter_test.cpp
 copy 
regression-test/suites/{inverted_index_p1/index_compaction/test_index_compaction_p1.groovy
 => 
inverted_index_p0/index_compaction/test_index_compaction_empty_segments.groovy} 
(56%)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to