Tags: apache/datafusion
Tags
[branch-52] Update version to 52.4.0 and update changelog (#21004)
[branch-53]: fix `array_remove_*` with NULLS (#21013) (#21016) ## 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 #21011 . ## Rationale for this change Handle correctly `array_remove_*` functions if NULL is a value to delete <!-- 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. --> (cherry picked from commit 6ab16cc) ## 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. --> ## 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. -->
[branch-53] Update Release Notes (#20952) ## Which issue does this PR close? - Part of #19692 ## Rationale for this change We have backported a bunch of bug fixes to branch-53, so let's make sure the release notes reflect that ## What changes are included in this PR? I ran ```shell uv run ./dev/release/generate-changelog.py 52.3.0 branch-53 53.0.0 > dev/changelog/53.0.0.md ``` And then had codex review via ``` › Please review dev/changelog/53.0.0.md to ensure it reflects all commits between where `apache/branch-53` and `main` diverged ``` Then I updated the change log to reflect the original authors not the backport authors ## Are these changes tested? By CI
[branch-53] Update Release Notes (#20952) ## Which issue does this PR close? - Part of #19692 ## Rationale for this change We have backported a bunch of bug fixes to branch-53, so let's make sure the release notes reflect that ## What changes are included in this PR? I ran ```shell uv run ./dev/release/generate-changelog.py 52.3.0 branch-53 53.0.0 > dev/changelog/53.0.0.md ``` And then had codex review via ``` › Please review dev/changelog/53.0.0.md to ensure it reflects all commits between where `apache/branch-53` and `main` diverged ``` Then I updated the change log to reflect the original authors not the backport authors ## Are these changes tested? By CI
[branch-52] Bump to 52.3.0 and changelog (#20790) ## 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. --> - Related to #20681 ## 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. --> ## What changes are included in this PR? Bumps to 52.3.0 and changelog <!-- 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: Haresh Khanna <[email protected]> Co-authored-by: Tim Saucer <[email protected]>
[branch-52] Bump to 52.3.0 and changelog (#20790) ## 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. --> - Related to #20681 ## 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. --> ## What changes are included in this PR? Bumps to 52.3.0 and changelog <!-- 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: Haresh Khanna <[email protected]> Co-authored-by: Tim Saucer <[email protected]>
[branch-52] Update version and prepare changelog (#20560) ## Which issue does this PR close? - part of #20287 ## Rationale for this change Prepare for release ## What changes are included in this PR? 1. Update version 2. prepare CHANGELOG. See rendered version here: https://github.com/alamb/datafusion/blob/alamb/prepare_52.2.0/dev/changelog/52.2.0.md I'll have to update this at least once more once we merge the other outstanding PRs: ```shell ./dev/release/generate-changelog.py 52.1.0 branch-52 52.2.0 > dev/changelog/52.2.0.md npx [email protected] -w dev/changelog/52.2.0.md ``` Note the security audit CI check will fail until we merge - #20546 ## Are these changes tested? By CI ## 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: Oleks V <[email protected]>
[branch-52] Update version and prepare changelog (#20560) ## Which issue does this PR close? - part of #20287 ## Rationale for this change Prepare for release ## What changes are included in this PR? 1. Update version 2. prepare CHANGELOG. See rendered version here: https://github.com/alamb/datafusion/blob/alamb/prepare_52.2.0/dev/changelog/52.2.0.md I'll have to update this at least once more once we merge the other outstanding PRs: ```shell ./dev/release/generate-changelog.py 52.1.0 branch-52 52.2.0 > dev/changelog/52.2.0.md npx [email protected] -w dev/changelog/52.2.0.md ``` Note the security audit CI check will fail until we merge - #20546 ## Are these changes tested? By CI ## 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: Oleks V <[email protected]>
[branch-52] Update version to `52.1.0` (#19878) ## Which issue does this PR close? - part of #19784 ## Rationale for this change Prepare for release ## What changes are included in this PR? Update release version to 52.1.0 and add changelog ## Are these changes tested? By CI ## Are there any user-facing changes? New version
PreviousNext