Skip to content

Comments

Update release notes for 0.289 - Added fix to avoid pushdown of negat…#23733

Closed
jp-sivaprasad wants to merge 1 commit intoprestodb:masterfrom
jp-sivaprasad:release-notes-0.289
Closed

Update release notes for 0.289 - Added fix to avoid pushdown of negat…#23733
jp-sivaprasad wants to merge 1 commit intoprestodb:masterfrom
jp-sivaprasad:release-notes-0.289

Conversation

@jp-sivaprasad
Copy link
Contributor

Update release notes for 0.289 - Added fix to avoid pushdown of negative position for element_at as subfield pruning for array

Description

Update release notes for 0.289 - Added fix to avoid pushdown of negative position for element_at as subfield pruning for array. PR: 23479

== NO RELEASE NOTE ==

…ive position for element_at as subfield pruning for array. PR:23479
* Fix array_min/array_max when the first element recursively contains an inner array with a null element. :pr:`23323`
* Fix :func:`map_top_n` function to be deterministic by using keys to break ties. :pr:`22778`
* Fix stddev and variance functions to always return correct results when input is constant. :pr:`23447`
* Fix to avoid pushdown of negative position for element_at as subfield pruning for array, so as to allow query with negative array subscript to succeed. :pr:`23479`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Fix to avoid pushdown of negative position for element_at as subfield pruning for array, so as to allow query with negative array subscript to succeed. :pr:`23479`
* Fix filter pushdown of negative array positions. :pr:`23479`

@wanglinsong
Copy link
Member

The PR is not in branch release-0.289.
Avoid pushdown of negative position for element_at as subfield pruning for array #23479

@steveburnett
Copy link
Contributor

The PR is not in branch release-0.289. Avoid pushdown of negative position for element_at as subfield pruning for array #23479

Thanks for checking @wanglinsong! Given that information, I think that

@jp-sivaprasad
Copy link
Contributor Author

Closing, as this change will be part of 0.290 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants