berkaysynnada opened a new pull request, #7383:
URL: https://github.com/apache/arrow-datafusion/pull/7383
## 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.
-->
In the interval arithmetic library, there is a function converting open
bounds to closed bounds for convenience. This function increments or decrements
a bound's value (according to the side of the bound) one step-size of the
corresponding datatype. However, some buggy cases have been realized:
1) When a floating point value is 0 and it is tried to be decremented
2) When a value is tried to be incremented when it is at its maximum
3) When a value is tried to be decremented when it is at its minimum
After the fix, when an integer is at its maximum/minimu, it remains the
same. When a floating value is at its maximum/minimum, it becomes
infinity/negative infinity.
## 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.
-->
There are minor changes in the implementation of next_value() function. The
existing next_up()/next_down() functions are used for floating point values,
while integers are checked firstly if they are at min/max.
## 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.
## 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]
