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

airborne12 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris.git


The following commit(s) were added to refs/heads/master by this push:
     new b12d2a0b530 [test](be) Use storage block creation in bloom filter FPP 
writer test (#67090)
b12d2a0b530 is described below

commit b12d2a0b530cd6c8c8db66322f24fcc9a4d5941a
Author: hoshinojyunn <[email protected]>
AuthorDate: Tue Aug 25 14:27:01 2026 +0800

    [test](be) Use storage block creation in bloom filter FPP writer test 
(#67090)
    
    ### What problem does this PR solve?
    
    Issue Number: None
    
    Related PR: #66472; #64652
    
    Problem Summary: TabletSchema::create_block() was removed during the
    read schema refactor, leaving bloom_filter_fpp_writer_test unable to
    compile. This updates the test to use create_storage_block(), which
    constructs the same physical schema columns, data types, and names
    required before default values are inserted.
---
 be/test/storage/segment/bloom_filter_fpp_writer_test.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/be/test/storage/segment/bloom_filter_fpp_writer_test.cpp 
b/be/test/storage/segment/bloom_filter_fpp_writer_test.cpp
index ad46d7222de..ff16ebe1ac0 100644
--- a/be/test/storage/segment/bloom_filter_fpp_writer_test.cpp
+++ b/be/test/storage/segment/bloom_filter_fpp_writer_test.cpp
@@ -154,7 +154,7 @@ const std::vector<ScalarBloomFilterTypeCase> 
kSegmentWriterCompatibleBloomFilter
         create_segment_writer_compatible_type_cases();
 
 Block create_single_row_default_block(const TabletSchemaSPtr& schema) {
-    Block block = schema->create_block();
+    Block block = schema->create_storage_block();
     for (uint32_t cid = 0; cid < schema->num_columns(); ++cid) {
         auto column = block.get_by_position(cid).column->assert_mutable();
         column->insert_default();


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

Reply via email to