Skip to content
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 452 release notes #22573

Merged
merged 2 commits into from
Jul 12, 2024
Merged

Add Trino 452 release notes #22573

merged 2 commits into from
Jul 12, 2024

Conversation

colebow
Copy link
Member

@colebow colebow commented Jul 3, 2024

Description

Assemble the release notes for the upcoming Trino 452 release.

Verification for each pull request

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

27 June 2024

28 June 2024

30 June 2024

1 July 2024

2 July 2024

3 July 2024

4 July 2024

5 July 2024

6 July 2024

7 July 2024

8 July 2024

9 July 2024

10 July 2024

11 July 2024

@cla-bot cla-bot bot added the cla-signed label Jul 3, 2024
@colebow colebow marked this pull request as ready for review July 3, 2024 19:38
docs/src/main/sphinx/release/release-452.md Show resolved Hide resolved
## General

* Fix query plans occasionally not rendering the stage details page. ({issue}`22542`)
* Fix a performance regression when using the native filesystem for Azure. ({issue}`22561`)
Copy link
Member

Choose a reason for hiding this comment

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

Dont we do that in the connectors normally?

Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

What connectors would this go to? It's just a filesystem, yeah?

Copy link
Contributor

Choose a reason for hiding this comment

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

Lake Connectors.

docs/src/main/sphinx/release/release-452.md Outdated Show resolved Hide resolved
docs/src/main/sphinx/release/release-452.md Outdated Show resolved Hide resolved
## General

* Fix query plans occasionally not rendering the stage details page. ({issue}`22542`)
* Fix a performance regression when using the native filesystem for Azure. ({issue}`22561`)
Copy link
Member

Choose a reason for hiding this comment

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

docs/src/main/sphinx/release/release-452.md Outdated Show resolved Hide resolved
docs/src/main/sphinx/release/release-452.md Show resolved Hide resolved
@colebow colebow force-pushed the colebow/rn-452 branch 2 times, most recently from 55ff5f1 to c4355f5 Compare July 11, 2024 17:37
@colebow colebow requested a review from martint July 11, 2024 17:38
docs/src/main/sphinx/release/release-452.md Show resolved Hide resolved

## Hive connector

* Add support for coercion of structural data types for non-partitioned tables
Copy link
Member

Choose a reason for hiding this comment

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

Is this related to being able to read columns where the declared type doesn't match the format of the data? If so, we don't describe is as "coercion" -- that's something the engine does to handle type promotion in expressions. See previous releases for related wording.

Copy link
Member

Choose a reason for hiding this comment

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

@Praveen2112, is this similar to the item about varbinary vs varchar?

* Add support for coercion of structural data types for non-partitioned tables
using ORC files. ({issue}`22326`)
* Add support for type coercion when adding new columns. ({issue}`19708`)
* Add support for `varbinary` to `varchar` type coercion. ({issue}`22322`)
Copy link
Member

Choose a reason for hiding this comment

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

Same as above.

docs/src/main/sphinx/release/release-452.md Show resolved Hide resolved
docs/src/main/sphinx/release/release-452.md Outdated Show resolved Hide resolved
docs/src/main/sphinx/release/release-452.md Outdated Show resolved Hide resolved
* Add support for coercion of structural data types for non-partitioned tables
using ORC files. ({issue}`22326`)
* Add support for type coercion when adding new columns. ({issue}`19708`)
* Add support for reading `varbinary` values as `varchar` columns in Trino. ({issue}`22322`)
Copy link
Member

Choose a reason for hiding this comment

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

This one doesn't make a lot of sense to me. Whose "varbinary" type? Hive's? Under what circumstances would that happen?

This seems related to previous changes to allow updating the schema of a table without rewriting all past data. If so, it should be rephrased as "allow changing a column type from varbinary to varchar".

cc @Praveen2112


## Hive connector

* Add support for coercion of structural data types for non-partitioned tables
Copy link
Member

Choose a reason for hiding this comment

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

@Praveen2112, is this similar to the item about varbinary vs varchar?

@martint martint dismissed mosabua’s stale review July 12, 2024 01:59

Comments addressed

@martint martint merged commit 6c01c52 into trinodb:master Jul 12, 2024
6 checks passed
@github-actions github-actions bot added this to the 452 milestone Jul 12, 2024
@colebow colebow deleted the colebow/rn-452 branch July 22, 2024 18:29
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.

4 participants