Add release notes for 0.294 #25633
Add release notes for 0.294 #25633
Conversation
prestodb-ci
requested review from
steveburnett,
elharo and
a team
as code owners
github-project-automation
bot
moved this from 🆕 Unprioritized
to 🏗 In progress
in Presto Documentation
|
I am done with my initial reviews and have applied my changes. I have pulled the updated branch, made a new doc build, and reviewed the new doc build from beginning to end each time. This PR is ready for the Release Note Shepherd. What I did:
|
|
There is currently no one identified as the Release Note Shepherd for 0.294. A volunteer from the Presto committers is requested. I believe that the work remaining in this PR for the Shepherd is:
|
| * Add pushdownSubfieldArgIndex parameter to ComplexTypeFunctionDescriptor for subfield optimization during query planning. `#25175 <https://github.com/prestodb/presto/pull/25175>`_ | ||
| * Add xxhash64 override with seed argument. `#25521 <https://github.com/prestodb/presto/pull/25521>`_ | ||
| * Adds aggregation tests from ``presto-tests`` to run with native query runner in ``presto-native-tests``. `#24809 <https://github.com/prestodb/presto/pull/24809>`_ | ||
| * Move UnnestNode to SPI, make it available in collector optimizer. `#25317 <https://github.com/prestodb/presto/pull/25317>`_ |
There was a problem hiding this comment.
This entry does not begin with a keyword in the Order of changes in the Release Notes Guidelines. I'd like this revised to follow that list. Ideally I ask that this be revised to explain to an end user of Presto, as described in Audience.
There was a problem hiding this comment.
@yhwang, would you look at revising this one? I wasn't sure what to do with it.
|
@tdcmeehan, a shepherd is needed for this PR for the 0.294 release. Also, there are several entries that I think would benefit from your attention to making them intelligible to an end user of Presto, which is something you've focused on in the last several release notes PRs to good result. In the interests of velocity I'd ask you to, when you have time, review the existing entries with your focus on that aspect. |
|
@yhwang, when you have time would you address this? The work to do is listed in this comment. Thanks! |
|
hi @steveburnett update the release notes for those missing items:
also went through the whole list and light touched some of them. compiled the doc and checked the release note in html format. |
There was a problem hiding this comment.
Thanks for the update @yhwang! Only a few minor requests. Also, please select some notable entries that you feel worthy to copy into the Highlights section.
| * Add pushdownSubfieldArgIndex parameter to ComplexTypeFunctionDescriptor for subfield optimization during query planning. `#25175 <https://github.com/prestodb/presto/pull/25175>`_ | ||
| * Add xxhash64 override with seed argument. `#25521 <https://github.com/prestodb/presto/pull/25521>`_ | ||
| * Adds aggregation tests from ``presto-tests`` to run with native query runner in ``presto-native-tests``. `#24809 <https://github.com/prestodb/presto/pull/24809>`_ | ||
| * Move UnnestNode to SPI, make it available in collector optimizer. `#25317 <https://github.com/prestodb/presto/pull/25317>`_ |
There was a problem hiding this comment.
@yhwang, would you look at revising this one? I wasn't sure what to do with it.
|
Hi @steveburnett add items to the highlights section. For #25317 I directly use the one that you suggested in the issue. It's hard for me to pick items for the highlights section. I hope it's a good list. Please feel free to revise the list if you see fit. |
There was a problem hiding this comment.
Thanks for your work @yhwang! Looks good. The commits need to be squashed before merge, but the words, format, order of sections, order of changes, and links all look good.
@tdcmeehan PTAL.
github-project-automation
bot
moved this from 🏗 In progress
to ✅ Done
in Presto Documentation
yhwang
force-pushed
the
release-notes-0.294
branch
from
0d3ae94 to
72e506c
Compare
|
Hi @steveburnett, I squashed commits, fixed one minor typo, and put two of us as authors in the commit. Thanks for the guidance and review! |
|
@tdcmeehan, please review. |
|
@rschlussel @arhimondr Can you help review this? Thanks! |
| * Improve efficiency of output buffer implementation to reduce memory usage in writer. `#24913 <https://github.com/prestodb/presto/pull/24913>`_ | ||
| * Improve query resource usage by enabling subfield pushdown for :func:`map_filter` when selected keys are constants. `#25451 <https://github.com/prestodb/presto/pull/25451>`_ | ||
| * Improve query resource usage by enabling subfield pushdown for :func:`map_subset` when the input array is a constant array. `#25394 <https://github.com/prestodb/presto/pull/25394>`_ | ||
| * Improve serialized size estimation by introducing a batched API using vectorized operations. It delivers up to 8x faster size estimation compared to the previous row-by-row implementation. Workloads with high serialization cost will benefit from adopting this range-based API. `#25569 <https://github.com/prestodb/presto/pull/25569>`_ |
There was a problem hiding this comment.
I am having trouble understanding what is the practical meaning of this. What does it mean for users?
There was a problem hiding this comment.
how about?
Improve the efficiency of queries that involve with serialization operator by processing data in large group instead of one by one.
| * Add property ``native_query_memory_reclaimer_priority`` which controls which queries are killed first when a worker is running low on memory. Higher value means lower priority to be consistent with velox memory reclaimer's convention. `#25325 <https://github.com/prestodb/presto/pull/25325>`_ | ||
| * Add pushdownSubfieldArgIndex parameter to ComplexTypeFunctionDescriptor for subfield optimization during query planning. `#25175 <https://github.com/prestodb/presto/pull/25175>`_ | ||
| * Add case-sensitive support for column names. It can be enabled for JDBC based connector by setting ``case-sensitive-name-matching=true`` at the catalog level. `#24983 <https://github.com/prestodb/presto/pull/24983>`_ | ||
| * Replace ``EXPLAIN (TYPE DISTRIBUTED)`` with ``EXPLAIN (TYPE VALIDATE)`` for faster, lightweight analysis. `#25545 <https://github.com/prestodb/presto/pull/25545>`_ |
There was a problem hiding this comment.
I'd add some context that this is for the Presto Router and in the context of C++/Java routing.
There was a problem hiding this comment.
I am not sure about this one, I thought this speeds up the explain query. not sure about router.
There was a problem hiding this comment.
@pdabre12 can you help explain this better in the context of the router?
There was a problem hiding this comment.
Does this work?
Updated presto-plan-checker-router-plugin router plugin to use EXPLAIN (TYPE VALIDATE) in place of EXPLAIN (TYPE DISTRIBUTED) , enabling faster routing of queries to either native or Java clusters.
github-project-automation
bot
moved this from ✅ Done
to 🏗 In progress
in Presto Documentation
|
@yhwang, please address @tdcmeehan's review of the Highlights. Because some of the feedback involves rewriting the entry, please make the same changes to the duplicate entries where they were copied from into the Highlights. |
Add release notes for 0.294 Co-authored-by: Steve Burnett <[email protected]> Co-authored-by: Timothy Meehan <[email protected]> Co-authored-by: Yihong Wang <[email protected]> Signed-off-by: Yihong Wang <[email protected]>
yhwang
force-pushed
the
release-notes-0.294
branch
from
72e506c to
8568801
Compare
|
@tdcmeehan thanks for the comments. I didn't think about user's perspective. and both you and @steveburnett remind me about that. addressed your comments for highlight section and left two question. |
|
@tdcmeehan , again, thanks for the comments. Addressed all your comments and waiting for inputs from the following PRs:
|
yhwang
force-pushed
the
release-notes-0.294
branch
from
2bee16b to
a889134
Compare
Signed-off-by: Yihong Wang <[email protected]>
yhwang
force-pushed
the
release-notes-0.294
branch
from
a889134 to
2b77af4
Compare
|
Update the notes again:
See the list here |
github-project-automation
bot
moved this from 🏗 In progress
to ✅ Done
in Presto Documentation
|
Thanks a lot @yhwang for driving this! |
github-project-automation
bot
moved this from ✅ Done
to 🏗 In progress
in Presto Documentation
There was a problem hiding this comment.
LGTM! (docs)
Pull updated branch, new local doc build, reviewed page in new local doc build. Looks great.
Thanks @yhwang and @tdcmeehan!
github-project-automation
bot
moved this from 🏗 In progress
to ✅ Done
in Presto Documentation
|
Hi @tdcmeehan can we have your LGTM again? And I learned a lot. I can do better the second time. Also, many thanks to @steveburnett |
You did a great job this time! |
Signed-off-by: Yihong Wang <[email protected]> Co-authored-by: Steve Burnett <[email protected]> Co-authored-by: Timothy Meehan <[email protected]> Co-authored-by: Yihong Wang <[email protected]>
Missing Release Notes
Gary Helmling
Shakyan Kushwaha
Zhichen Xu
github username
Extracted Release Notes
TIMESTAMPcolumn type by changing it from PrestoTIMESTAMPtype toTIMESTAMP_WITH_TIME_ZONE.TIMESTAMP_NTZcolumn type as PrestoTIMESTAMPtype.legacy_timestampshould be set tofalseto match delta type specifications. With it set,TIMESTAMPwill not adjust based on local timezone.case-sensitive-name-matching.case-sensitive-name-matching=trueconfiguration in the catalog configuration.TestAggregationsto native-tests #24809 (Author: Pramod Satya): [native] AddTestAggregationsto native-testspresto-teststo run with native query runner inpresto-native-tests.ANALYZE.case-sensitive-name-matching=trueat the catalog level.presto-plan-checker-router-plugin#25035 (Author: Pratik Joseph Dabre): Add a new custom router scheduler plugin :presto-plan-checker-router-pluginPresto Plan Checker Router Scheduler Plugin <https://github.com/prestodb/presto/tree/master/presto-plan-checker-router-plugin/README.md>_.MinMaxByToWindowFunctionto rewrite min_by/max_by aggregations with row_number window function.rename viewfor Iceberg connector when configured withRESTandNESSIE.RouterRequestInfoto get the URL destination.connector/hive:Quick Stats.com.amazonaws.util.StringUtils. Addaws-java-sdk-coreas a runtime dependency to support Redshift JDBC driver (v2.1.0.32) which relies on this class for metadata operations.$deletedmetadata column.$delete_file_pathmetadata column.$data_sequence_numbermetadata column for table with equality deletes.connector/hive:Avro Configuration Propertiesto Hive Connector documentation.CVE-2025-27817 <https://github.com/advisories/GHSA-vgq5-3255-v292>_. :pr:25312.native_query_memory_reclaimer_prioritywhich controls which queries are killed first when a worker is running low on memory. Higher value means lower priority to be consistent with velox memory reclaimer's convention.SHOW CREATE TABLE,SHOW CREATE VIEW,SHOW COLUMNS, andDESCRIBEqueries.map_subsetwhen the input array is a constant array.hive.copy-on-first-write-configuration-enabledto false (:issue:25404).MinMaxByToWindowFunctionoptimizer to cover cases where aggregation is on both map/array and non map/array types.map_filterwhen selected keys are constants.iceberg.delete-as-join-rewrite-max-delete-columnsconfiguration property anddelete_as_join_rewrite_max_delete_columnssession property to control when equality delete as join optimization is applied. The optimization is now only applied when the number of equality delete columns is less than or equal to this threshold (default: 400). Setting this to 0 disables the optimization. See :doc:/connector/icebergfor details.iceberg.delete-as-join-rewrite-enabledconfiguration property anddelete_as_join_rewrite_enabledsession property. Useiceberg.delete-as-join-rewrite-max-delete-columnsinstead.dot_productto calculate to calculate the sum of element wise product between two identically sized vectors represented as arrays. This function supports both array(real) and array(double) input types. For more information, refer to the Dot Product definition.parse_durationfunction for large millisecond values.EXPLAIN (TYPE DISTRIBUTED)withEXPLAIN (TYPE VALIDATE)for faster, lightweight analysis.CVE-2025-48924 <https://github.com/advisories/GHSA-j288-q9x7-2f5v>.TableLocationProviderinterface to decouple table location logic from JDBC configuration.All Commits
isEqualFunctionin FunctionResolution (wangd)AbstractTestQueriestestcases for native-tests (Pramod Satya)AbstractHiveSslTest(Tim Meehan)