-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Add Trino 479 release notes #27153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Add Trino 479 release notes #27153
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bfb4d64 to
d86980e
Compare
|
@wendigo @martint I am not add RN for #27341, could you confirm that #27341 (comment) by @findepi |
| * Improve performance of `repeat` function. ({issue}`27369`) | ||
| * Improve performance of data exchanges by using SIMD instructions on x86 CPUs that support the required extensions. This can be disabled by setting `experimental.blockserde-vectorized-null-suppression-strategy=NONE`({issue}`26919`) | ||
| * Fix planning failure of certain queries where part of the plan is optimized to empty values. ({issue}`21506`) | ||
| * Fix configuring partitioned layout for spooling protocol ({issue}`27247`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix server startup failure when partitioned spooling is configured.
This is spooling-filesystem plugin change. Still in General section?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @wendigo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wendigo please help to confirm if it is still suitable in the general section
1eb2398 to
ee6fb0f
Compare
|
squashed commits & fix format |
783f6ff to
92a0022
Compare
a3a058c to
5e735f1
Compare
12c978c to
dd29cf9
Compare
f3febb5 to
84c834e
Compare
|
(Squash commits for next round review) |
|
|
||
| * Generate TLS certificates for internal cluster communications automatically when node discovery type is set to `ANNOUNCE`. ({issue}`27030`) | ||
| * Add support for specifying the location of the Exchange Manager configuration file. ({issue}`26611`) | ||
| * Publish time taken by query in `FINISHING` state in event listener. ({issue}`27202`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to event listener
| * Add {func}`array_first` and {func}`array_last` functions. ({issue}`27295`) | ||
| * {{breaking}} The configuration property `task.statistics-cpu-timer-enabled` is now defunct and must be removed. ({issue}`27504`) | ||
| * Allow field name declaration in ROW literal. For example, `row(1 as a, 2 as b)` is now legal. ({issue}`25261`) | ||
| * Deprecate `EXPLAIN (TYPE LOGICAL)`. `EXPLAIN (TYPE DISTRIBUTED)` should be used instead. ({issue}`27434`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, both should be deprecated, since there's no longer a distinction between them. Really, we should consolidate both under a new type (say, PLAN) that's the default selection if no type is specified.
We don't need to do anything from an implementation perspective at this point though. We can just say that TYPE = DISTRIBUTED or LOCAL are deprecated and that EXPLAIN should be used to get the query plan.
| * {{breaking}} The configuration property `task.statistics-cpu-timer-enabled` is now defunct and must be removed. ({issue}`27504`) | ||
| * Allow field name declaration in ROW literal. For example, `row(1 as a, 2 as b)` is now legal. ({issue}`25261`) | ||
| * Deprecate `EXPLAIN (TYPE LOGICAL)`. `EXPLAIN (TYPE DISTRIBUTED)` should be used instead. ({issue}`27434`) | ||
| * Remove `prefer_streaming_operators` session property. `SET SESSION task_concurrency=1` can be used to achieve the same behaviour as `prefer_streaming_operators`. ({issue}`27506`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That effect is an unspecified and possibly unintended behavior. We don't need to include that.
| * Allow field name declaration in ROW literal. For example, `row(1 as a, 2 as b)` is now legal. ({issue}`25261`) | ||
| * Deprecate `EXPLAIN (TYPE LOGICAL)`. `EXPLAIN (TYPE DISTRIBUTED)` should be used instead. ({issue}`27434`) | ||
| * Remove `prefer_streaming_operators` session property. `SET SESSION task_concurrency=1` can be used to achieve the same behaviour as `prefer_streaming_operators`. ({issue}`27506`) | ||
| * Improve performance of remote data exchanges on CPUs supporting the required SIMD extensions. This can be disabled by setting `exchange.experimental.vectorized-serde.enabled=false`. ({issue}`27426`, {issue}`26919`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's rephrase as:
Add experimental performance improvements for remote data exchanges on newer CPU architectures, such as Graviton 3+, Skylake, Icelake, or Zen 4+. This can be disabled [...]
| * Improve performance of data exchanges involving variable width data. ({issue}`27377`) | ||
| * Fix planning failure of certain queries where part of the plan is optimized to empty values. ({issue}`21506`) | ||
| * Fix configuring partitioned layout for spooling protocol. ({issue}`27247`) | ||
| * Fix `EXPLAIN (TYPE IO)` failure when query constraint contains type which cannot be cast to `varchar`. ({issue}`27433`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... when the WHERE clause involves a type which cannot be cast to
varchar
|
|
||
| ## BigQuery connector | ||
|
|
||
| * Fix query failure when reusing `query` table function result. ({issue}`27573`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Link to the function docs
|
|
||
| ## ClickHouse connector | ||
|
|
||
| * Replace `join-pushdown.with-expressions` configuration property with `deprecated.join-pushdown.with-expressions`. The new property will be removed in a future version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to fix the code here. We should mark the property with LegacyConfig as I mentioned above so that users get a warning at startup time that the property is deprecated and not mention anything in the release notes.
| * Rename `s3.exclusive-create` config to `delta.s3.transaction-log-conditional-writes.enabled`. ({issue}`27372`) | ||
| * Fix incorrect results for queries involving `IS NOT DISTINCT FROM`. ({issue}`27213`) | ||
| * Fix failure when writing to tables created by Databricks 17.3. ({issue}`27100`) | ||
| * Fix failure when checking Azure hierarchical namespaces to avoid requiring additional storage permissions. ({issue}`27278`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The phrasing sounds weird. It read as if there's a failure that results in requiring additional storage permissions (which makes little sense), and that we're fixing such failure so that the user doesn't have to specify additional storage permissions 🤔. Is the "to" meant to be an "and"?
TL;DR, I have no idea what this is about from reading the item. It's probably simpler to just say "Fix failure when checking Azure hierarchical namespaces".
| * Add support for updating [token-exchange-enabled](https://iceberg.apache.org/docs/nightly/configuration/#oauth2-auth-properties) via the `iceberg.rest-catalog.oauth2.token-exchange-enabled` config property. ({issue}`27174`) | ||
| * Add `retain_last` and `clean_expired_metadata` options to `expire_snapshots` command. ({issue}`27357`) | ||
| * Add `APPLICATION_DEFAULT` authentication type for GCS. ({issue}`26984`) | ||
| * Remove `s3.exclusive-create` config. ({issue}`27372`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did the config option do anything? If so, what functionality is being removed? If not, there's no point in mentioning it.
| ## Memory connector | ||
|
|
||
| * Add support for setting and dropping column defaults via `ALTER TABLE ... ALTER COLUMN`. ({issue}`26162`) | ||
| * Fixed `RENAME SCHEMA` in the memory connector when there is more than one table in the schema. ({issue}`27205`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- "Fix" instead of "fixed"
- What does it fix? A failure? Corruption? Incorrect results?
- No need to mention "memory connector". It's self evident, since it's in the memory connector section
Description
Additional context and related issues
The entry are not added yet
#27341
#27340
#27133
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.
Format: PR/issue number, ✅ / ❌ rn ✅ / ❌ docs
✅ rn - release note added and verified, or assessed to be not necessary, set to ❌ rn before completion
✅ docs - need for docs assessed and merged, or assessed to be not necessary, set to ❌ docs before completion
29 Oct 2025
30 Oct 2025
31 Oct 2025
1 Nov 2025
2 Nov 2025
03 Nov 2025
2150604 Nov 2025
kill_query#27055 ✅ rn ✅ docs05 Nov 2025
06 Nov 2025
RemoveTrivialFilterscallRemoveEmptyUnionBranchesto prune empty union branches. #26349 ✅ rn ✅ docs - covered in2150607 Nov 2025
09 Nov 2025
10 Nov 2025
11 Nov 2025
12 Nov 2025
13 Nov 2025
14 Nov 2025
15 Nov 2025
16 Nov 2025
17 Nov 2025
18 Nov 2025
19 Nov 2025
20 Nov 2025
retain_lastandclean_expired_metadataoptions to Icebergexpire_snapshotstable procedure #27362 ✅ rn✅ docs21 Nov 2025
SET DEFAULTandDROP DEFAULTstatements #26162 ✅ rn ✅ docss3.exclusive-createconfig with Delta Lake's one #27372 ✅ rn ✅ docs22 Nov 2025
array_firstandarray_lastfunctions #27295 ✅ rn ✅ docs23 Nov 2025
24 Nov 2025
APPLICATION_DEFAULTauthentication type for GCS #27106 ❌ ✅ docs25 Nov 2025
26 Nov 2025
Sessionparam fromConnectorServicesProvider#27447 ✅ rn ✅ docs27 Nov 2025
EXPLAIN (TYPE IO)failure when constraint contains type which cannot be cast tovarchar#27433 ✅ rn ✅ docs28 Nov 2025
mainsyntax to Java 25 #27495 ✅ rn ✅ docs29 Nov 2025
30 Nov 2025
01 Dec 2025
02 Dec 2025
03 Dec 2025
org.assertj.core.util.VisibleForTestingwith Guava's #27543 ✅ rn ✅docsWHEN STALEsyntax forCREATE MATERIALIZED VIEW#27356 ✅ rn ✅docs04 Dec 2025
05 Dec 2025
08 Dec 2025
selectquery when reusing BigQueryquerytable function result #27578 ❌ ✅docs09 Dec 2025
10 Dec 2025