berkaysynnada opened a new pull request, #7417:
URL: https://github.com/apache/arrow-datafusion/pull/7417
## 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.
-->
After `ProjectionExec` is able to propagate the orders of non-column
expressions, it is also possible to preserve the order of some
`ScalarFunctionExpr`'s. This PR implements that feature.
This PR is the 3rd step of
https://github.com/apache/arrow-datafusion/pull/7296 and
https://github.com/apache/arrow-datafusion/pull/7364 PR's. Now, we have the
support of propagating the sort order over different kinds of `PhysicalExpr`'s
at the projection stage.
## What changes are included in this PR?
<!--
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.
-->
While creating `ScalarFunctionExpr`, we check its order preservation info
from `BuiltinScalarFunction`. `math_expressions` and `datetime_expressions`
are labeled according to their functional monotonicity. `ScalarFunctionExpr`
now has a field `monotonicity: Option<FuncMonotonicity>`. `FuncMonotonicity`
keeps monotonicity information of the function. It is one to one mapped to
`args` of the function, and it specifies the effect of an increase or decrease
in the corresponding `arg` to the function value.
## 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)?
-->
Yes, by .slt tests with some of the functions.
## Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!--
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]
