Re: [PR] [fix](pipeline) sub_running_sink_operators in close [doris]

2024-11-07 Thread via GitHub
Mryange commented on PR #43500: URL: https://github.com/apache/doris/pull/43500#issuecomment-2463931885 run buildall -- 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 unsu

Re: [PR] [fix](pipeline) sub_running_sink_operators in close [doris]

2024-11-07 Thread via GitHub
Mryange commented on PR #43500: URL: https://github.com/apache/doris/pull/43500#issuecomment-2463928443 run buildall -- 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 unsu

Re: [PR] [fix](pipeline) sub_running_sink_operators in close [doris]

2024-11-07 Thread via GitHub
doris-robot commented on PR #43500: URL: https://github.com/apache/doris/pull/43500#issuecomment-2463928366 Thank you for your contribution to Apache Doris. Don't know what should be done next? See [How to process your PR](https://cwiki.apache.org/confluence/display/DORIS/How+to+proce

[PR] [fix](pipeline) sub_running_sink_operators in close [doris]

2024-11-07 Thread via GitHub
Mryange opened a new pull request, #43500: URL: https://github.com/apache/doris/pull/43500 ### What problem does this PR solve? Previously, sub_running_sink_operators was called only when encountering EOS during sink or when all sources were closed. However, this approach has issues