Skip to content

Add Trino 381 release notes#12277

Merged
martint merged 1 commit intotrinodb:masterfrom
simpligility:rn-381
May 16, 2022
Merged

Add Trino 381 release notes#12277
martint merged 1 commit intotrinodb:masterfrom
simpligility:rn-381

Conversation

@mosabua
Copy link
Copy Markdown
Member

@mosabua mosabua commented May 6, 2022

Description

Assemble the release notes for the upcoming Trino 381 release.

Is this change a fix, improvement, new feature, refactoring, or other?

Improvement.

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

Documentation only.

How would you describe this change to a non-technical end user or system administrator?

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 ✅

8 May 2022 ✅

9 May 2022 ✅

10 May 2022 ✅

11 May 2022 ✅

12 May 2022 ✅

13 May 2022 ✅

14 May 2022 ✅

  • no commits

15 May 2022 ✅

16 May 2022 ✅

@mosabua
Copy link
Copy Markdown
Member Author

mosabua commented May 9, 2022

@arhimondr @oraclechang we need a suggestion for a release notes entry for #11885 , and confirmation that no docs are needed

@mosabua
Copy link
Copy Markdown
Member Author

mosabua commented May 9, 2022

@Praveen2112 @ksobolew we need a suggestion for a release notes entry for #12204 , and confirmation that no docs are needed - DONE ✅

@mosabua mosabua force-pushed the rn-381 branch 2 times, most recently from 710ec6c to 43152d9 Compare May 9, 2022 16:00
@ksobolew
Copy link
Copy Markdown
Contributor

@Praveen2112 @ksobolew we need a suggestion for a release notes entry for #12204 , and confirmation that no docs are needed

"Fixed a regression in file-based system and connector access controls" should be enough IMO

@mosabua mosabua force-pushed the rn-381 branch 2 times, most recently from 8278cd7 to a5cd4d8 Compare May 10, 2022 21:22
@mosabua mosabua force-pushed the rn-381 branch 2 times, most recently from 9e12911 to f4ce898 Compare May 11, 2022 03:43
@mosabua mosabua force-pushed the rn-381 branch 2 times, most recently from b7cf65a to 81e21ba Compare May 11, 2022 03:52
Copy link
Copy Markdown
Member

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`)

Copy link
Copy Markdown
Member Author

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..

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

@Praveen2112 .. is this okay?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Same here.

Copy link
Copy Markdown
Member Author

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

Copy link
Copy Markdown
Member Author

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

Copy link
Copy Markdown
Member Author

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

Copy link
Copy Markdown
Member

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"

@mosabua mosabua force-pushed the rn-381 branch 4 times, most recently from ebdf994 to 2f15db7 Compare May 16, 2022 17:45
@martint martint merged commit ecaea41 into trinodb:master May 16, 2022
@github-actions github-actions bot added this to the 381 milestone May 16, 2022
@mosabua mosabua deleted the rn-381 branch May 16, 2022 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

Release notes for 381

8 participants