-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Add Trino 381 release notes #12277
Add Trino 381 release notes #12277
Conversation
@arhimondr @oraclechang we need a suggestion for a release notes entry for #11885 , and confirmation that no docs are needed |
@Praveen2112 @ksobolew we need a suggestion for a release notes entry for #12204 , and confirmation that no docs are needed - DONE ✅ |
710ec6c
to
43152d9
Compare
"Fixed a regression in file-based system and connector access controls" should be enough IMO |
8278cd7
to
a5cd4d8
Compare
9e12911
to
f4ce898
Compare
b7cf65a
to
81e21ba
Compare
|
||
* Prevent data loss when non-transactional insert fails. ({issue}`12229`) | ||
|
||
## SingleStore (MemSQL) connector |
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.
add
* Prevent data loss when non-transactional insert fails. ({issue}`12229`)
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.
Ok .. added .. but question .. are you sure? How can we tell ourselves in the future. It seem that the SingleStore connector does not extend the JdbcPlugin .. which is what we used as criteria to create the list..
update failures. ({issue}`12187`) | ||
* Fix query failure when a table has multiple column masks defined. ({issue}`12262`) | ||
* Fix regression in file-based system and connector access controls. ({issue}`12204`) | ||
* Fix regression in LDAP password authenticator usage with ActiveDirectory. ({issue}`12231`) |
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.
@Praveen2112 .. is this okay?
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.
Same here.
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.
thats actually PR 12310 .. and if fixes the isseue 12321
I just removed "regression in" because from the PR I think this is a new fix .. please confirm @Praveen2112
|
||
## General | ||
|
||
* Add support for fault-tolerant execution with exchange spooling on Azure Blob Storage. ({issue}`12211`) |
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.
@arhimondr @losipiuk @jhlodin .. this PR introduces new properties and I am pretty sure we need a new section in the docs as well as those properties explained.. also need the same for GCS whenever that is coming.. can you please work on that documentation asap?
https://trino.io/docs/current/admin/fault-tolerant-execution.html#exchange-manager
Thx
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.
@colebow please file ticket to add docs for this
* Add support for automatic discovery of OpenID Connect metadata with OAuth 2.0 | ||
authentication. ({issue}`9788`) | ||
* Re-introduce `ldap.ssl-trust-certificate` as legacy configuration to avoid | ||
update failures. ({issue}`12187`) |
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.
My point is that "update failures" is ambiguous and could be confused with "failures for UPDATE queries"
ebdf994
to
2f15db7
Compare
Description
Assemble the release notes for the upcoming Trino 381 release.
Improvement.
Documentation only.
Add the release notes for Trino 381 with sections for general, security, connectors and other topics as included in the release.
Related issues, pull requests, and links
Documentation
( ) No documentation is needed.
(✅ ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
(✅ ) No release notes entries required.
( ) Release notes entries required with the following suggested text:
Verification for each commit
Format: commit, committer/maintainer, 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 merge, or assessed to be not necessary, set to ❌ docs before completion
7 May 2022 ✅
docs
8 May 2022 ✅
docs
9 May 2022 ✅
10 May 2022 ✅
11 May 2022 ✅
12 May 2022 ✅
13 May 2022 ✅
@VisibleForTesting
annotation #12363 ✅ rn ✅docs14 May 2022 ✅
15 May 2022 ✅
16 May 2022 ✅