waynexia opened a new pull request, #7166:
URL: https://github.com/apache/arrow-datafusion/pull/7166
# Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #.
# Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
I found these two places would break my execution somehow. From my
perspective they are allowed to be looser.
# What changes are included in this PR?
The change in pipeline checker uses `.unwrap_or(true)` to set the default
value of `unbounded_output()`. This change acts the same as in other places
https://github.com/apache/arrow-datafusion/blob/1b4153f1e229b1d6308427318b5f68d0ded8f2ab/datafusion/core/src/physical_optimizer/sort_enforcement.rs#L962
And the `AnalyzeExec` one would lead to an assertion failure in
https://github.com/apache/arrow-datafusion/blob/1b4153f1e229b1d6308427318b5f68d0ded8f2ab/datafusion/core/src/physical_optimizer/dist_enforcement.rs#L843-L845
But sadly I cannot reproduce this with `datafusion-cli`, and I haven't find
out the root cause.
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
# Are these changes tested?
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example, are
they covered by existing tests)?
-->
By existing tests. And I find that we don't have slt case for `explain
analyze`. Is there any blocker?
# Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
no
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
--
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]
