BiteTheDDDDt opened a new pull request, #19704: URL: https://github.com/apache/doris/pull/19704
…Ids updated # Proposed changes fix distributionColumnIds not updated correct when outputColumnUniqueIds updated ```cpp =1289431==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6020026feb18 at pc 0x55fc8e87fe87 bp 0x7f93a22ff3b0 sp 0x7f93a22ff3a8 READ of size 8 at 0x6020026feb18 thread T417 (_scanner_scan) #0 0x55fc8e87fe86 in doris::pipeline::PipScannerContext::append_blocks_to_queue(std::vector<std::unique_ptr<doris::vectorized::Block, std::default_delete<doris::vectorized::Block> >, std::allocator<std ::unique_ptr<doris::vectorized::Block, std::default_delete<doris::vectorized::Block> > > >&) /root/doris/be/src/vec/exec/scan/pip_scanner_context.h:88:48 #1 0x55fc8e6b48aa in doris::vectorized::ScannerScheduler::_scanner_scan(doris::vectorized::ScannerScheduler*, doris::vectorized::ScannerContext*, std::shared_ptr<doris::vectorized::VScanner>) /root/dor is/be/src/vec/exec/scan/scanner_scheduler.cpp:375:14 #2 0x55fc8e6b6d17 in doris::vectorized::ScannerScheduler::_schedule_scanners(doris::vectorized::ScannerContext*)::$_0::operator()() const::'lambda0'()::operator()() const /root/doris/be/src/vec/exec/sc an/scanner_scheduler.cpp:202:31 #3 0x55fc8e6b6d17 in void std::_invoke_impl<void, doris::vectorized::ScannerScheduler::_schedule_scanners(doris::vectorized::ScannerContext*)::$_0::operator()() const::'lambda0'()&>(std::_invoke_othe r, doris::vectorized::ScannerScheduler::_schedule_scanners(doris::vectorized::ScannerContext*)::$_0::operator()() const::'lambda0'()&) /var/local/ldb-toolchain/bin/../lib/gcc/x86_64-linux-gnu/11/../../../. ./include/c++/11/bits/invoke.h:61:14 #4 0x55fc8e6b6d17 in std::enable_if<is_invocable_r_v<void, doris::vectorized::ScannerScheduler::_schedule_scanners(doris::vectorized::ScannerContext*)::$_0::operator()() const::'lambda0'()&>, void>::ty pe std::__invoke_r<void, doris::vectorized::ScannerScheduler::_schedule_scanners(doris::vectorized::ScannerContext*)::$_0::operator()() const::'lambda0'()&>(doris::vectorized::ScannerScheduler::_schedule_s canners(doris::vectorized::ScannerContext*)::$_0::operator()() const::'lambda0'()&) /var/local/ldb-toolchain/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/bits/invoke.h:111:2 #5 0x55fc8e6b6d17 in std::Function_handler<void (), doris::vectorized::ScannerScheduler::_schedule_scanners(doris::vectorized::ScannerContext*)::$_0::operator()() const::'lambda0'()>::_M_invoke(std:: Any_data const&) /var/local/ldb-toolchain/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/bits/std_function.h:291:9 #6 0x55fc8e6be44c in std::function<void ()>::operator()() const /var/local/ldb-toolchain/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/bits/std_function.h:560:9 #7 0x55fc8e6be44c in doris::PriorityWorkStealingThreadPool::work_thread(int) /root/doris/be/src/util/priority_work_stealing_thread_pool.hpp:135:17 #8 0x55fc91fd3e3f in execute_native_thread_routine /data/gcc-11.1.0/build/x86_64-pc-linux-gnu/libstdc+-v3/src/c11/../../../../../libstdc-v3/src/c+11/thread.cc:82:18 #9 0x7f962b615608 in start_thread /build/glibc-SzIz7B/glibc-2.31/nptl/pthread_create.c:477:8 #10 0x7f962b8a4132 in __clone /build/glibc-SzIz7B/glibc-2.31/misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:95 ``` ## Problem summary Describe your changes. ## Checklist(Required) * [ ] Does it affect the original behavior * [ ] Has unit tests been added * [ ] Has document been added or modified * [ ] Does it need to update dependencies * [ ] Is this PR support rollback (If NO, please explain WHY) ## Further comments If this is a relatively large or complex change, kick off the discussion at [[email protected]](mailto:[email protected]) by explaining why you chose the solution you did and what alternatives you considered, etc... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
