Re: [PR] branch-4.0: [fix](nereids) PhysicalDictionarySink.resetLogicalProperties() does not reset logical properties properly #60495 [doris]
yiguolei commented on PR #60521: URL: https://github.com/apache/doris/pull/60521#issuecomment-3857404432 skip 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 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]
Re: [PR] branch-4.0: [fix](nereids) PhysicalDictionarySink.resetLogicalProperties() does not reset logical properties properly #60495 [doris]
yiguolei merged PR #60521: URL: https://github.com/apache/doris/pull/60521 -- 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]
Re: [PR] branch-4.0: [fix](nereids) PhysicalDictionarySink.resetLogicalProperties() does not reset logical properties properly #60495 [doris]
hello-stephen commented on PR #60521: URL: https://github.com/apache/doris/pull/60521#issuecomment-3851126726 # FE UT Coverage Report Increment line coverage ` 0.00% (0/1)` :tada: [Increment coverage report](http://coverage.selectdb-in.cc/coverage/60521_f78fffd7c5801784f015c21291060b7ea9cff92e/fe_increment_report/index.html) [Complete coverage report](http://coverage.selectdb-in.cc/coverage/60521_f78fffd7c5801784f015c21291060b7ea9cff92e/fe_report/index.html) -- 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]
Re: [PR] branch-4.0: [fix](nereids) PhysicalDictionarySink.resetLogicalProperties() does not reset logical properties properly #60495 [doris]
hello-stephen commented on PR #60521: URL: https://github.com/apache/doris/pull/60521#issuecomment-3850919483 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 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]
Re: [PR] branch-4.0: [fix](nereids) PhysicalDictionarySink.resetLogicalProperties() does not reset logical properties properly #60495 [doris]
dataroaring closed pull request #60521: branch-4.0: [fix](nereids) PhysicalDictionarySink.resetLogicalProperties() does not reset logical properties properly #60495 URL: https://github.com/apache/doris/pull/60521 -- 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]
Re: [PR] branch-4.0: [fix](nereids) PhysicalDictionarySink.resetLogicalProperties() does not reset logical properties properly #60495 [doris]
hello-stephen commented on PR #60521: URL: https://github.com/apache/doris/pull/60521#issuecomment-3850919307 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+process+your+PR). Please clearly describe your PR: 1. What problem was fixed (it's best to include specific error reporting information). How it was fixed. 2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be. 3. What features were added. Why was this function added? 4. Which code was refactored and why was this part of the code refactored? 5. Which functions were optimized and what is the difference before and after the optimization? -- 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]
