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

morrysnow pushed a commit to branch branch-3.1
in repository https://gitbox.apache.org/repos/asf/doris.git


The following commit(s) were added to refs/heads/branch-3.1 by this push:
     new 076362d7032 branch-3.1: [Fix](flexible partial update) Report error 
when multi segments are generated in one flexible partial update load #42688 
(#53422)
076362d7032 is described below

commit 076362d7032474e60a04ac0837658c90288cd75c
Author: bobhan1 <[email protected]>
AuthorDate: Thu Jul 17 13:47:11 2025 +0800

    branch-3.1: [Fix](flexible partial update) Report error when multi segments 
are generated in one flexible partial update load #42688 (#53422)
    
    pick #42688
---
 be/src/olap/rowset_builder.cpp | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/be/src/olap/rowset_builder.cpp b/be/src/olap/rowset_builder.cpp
index e3357e1a5e3..31506d1adfc 100644
--- a/be/src/olap/rowset_builder.cpp
+++ b/be/src/olap/rowset_builder.cpp
@@ -265,6 +265,16 @@ Status BaseRowsetBuilder::submit_calc_delete_bitmap_task() 
{
     }
     std::lock_guard<std::mutex> l(_lock);
     SCOPED_TIMER(_submit_delete_bitmap_timer);
+    if (_partial_update_info && 
_partial_update_info->is_flexible_partial_update()) {
+        if (_rowset->num_segments() > 1) {
+            // in flexible partial update, when there are more one segment in 
one load,
+            // we need to do alignment process for same keys between segments, 
we haven't
+            // implemented it yet and just report an error when encouter this 
situation
+            return Status::NotSupported(
+                    "too large input data in flexible partial update, Please "
+                    "reduce the amount of data imported in a single load.");
+        }
+    }
     auto* beta_rowset = reinterpret_cast<BetaRowset*>(_rowset.get());
     std::vector<segment_v2::SegmentSharedPtr> segments;
     RETURN_IF_ERROR(beta_rowset->load_segments(&segments));


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

Reply via email to