HappenLee opened a new pull request, #64703:
URL: https://github.com/apache/doris/pull/64703

   ### What problem does this PR solve?
   
   Issue Number: N/A
   
   Related PR: N/A
   
   Problem Summary: concat_ws has a BE execution path for a single array 
argument. When the array column row itself is NULL, the executor still walked 
the nested array data and could return values from nested storage instead of 
treating the NULL array row as empty input. Also, if the optimizer rewrite is 
disabled, multiple array arguments can reach this BE array path and were 
silently executed using only the first array argument. This change keeps 
concat_ws return nullability unchanged, skips nested data for NULL array rows, 
and rejects array-form concat_ws calls unless the executor receives exactly 
separator plus one array argument.
   
   ### Release note
   
   Fix wrong concat_ws results for nullable array inputs and return an error 
for unsupported multiple-array execution without optimizer rewrite.
   
   ### Check List (For Author)
   
   - Test: Regression test and build
       - ./build.sh --be
       - ./run-regression-test.sh --run --conf 
/tmp/doris-regression-conf-run-path.groovy -d 
nereids_function_p0/scalar_function -s nereids_scalar_fn_concat_ws -forceGenOut
       - ./run-regression-test.sh --run --conf 
/tmp/doris-regression-conf-run-path.groovy -d 
nereids_function_p0/scalar_function -s nereids_scalar_fn_concat_ws
   - Behavior changed: Yes. concat_ws skips nested data for NULL array rows, 
and unsupported multiple-array BE execution now returns INVALID_ARGUMENT 
instead of silently consuming only the first array.
   - Does this need documentation: No


-- 
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]

Reply via email to