Skip to content

chore: change width_bucket buckets parameter from i32 to i64#20330

Merged
comphead merged 1 commit intoapache:mainfrom
comphead:width-bucket-i64
Feb 13, 2026
Merged

chore: change width_bucket buckets parameter from i32 to i64#20330
comphead merged 1 commit intoapache:mainfrom
comphead:width-bucket-i64

Conversation

@comphead
Copy link
Contributor

Which issue does this PR close?

Rationale for this change

Change bucket datatype to be same as Spark

https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/mathExpressions.scala#L1864

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@github-actions github-actions bot added the spark label Feb 12, 2026
@comphead
Copy link
Contributor Author

Thanks @Jefffrey for the quick review

@comphead comphead added this pull request to the merge queue Feb 13, 2026
Merged via the queue into apache:main with commit a3d4651 Feb 13, 2026
54 checks passed
de-bgunter pushed a commit to de-bgunter/datafusion that referenced this pull request Mar 24, 2026
…20330)

## 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 apache#123` indicates that this PR will close issue apache#123.
-->

- Closes apache#20320 .

## Rationale for this change

Change `bucket` datatype to be same as Spark


https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/mathExpressions.scala#L1864

<!--
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.
-->

## 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.
-->

## 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)?
-->

## 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.
-->

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Spark width_bucket builtin functions wrong signature

2 participants