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 469 release notes #24509

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

Conversation

mosabua
Copy link
Member

@mosabua mosabua commented Dec 18, 2024

Description

Assemble the release notes for the upcoming Trino 469 release.

Additional context and related issues

See https://github.com/trinodb/trino/pulls?q=is%3Apr+is%3Aclosed+milestone%3A469

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.

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

18 Dec 2024

19 Dec 2024

20 Dec 2024

21 Dec 2024

22 Dec 2024

23 Dec 2024

24 Dec 2024

25 Dec 2024

26 Dec 2024

27 Dec 2024

28 Dec 2024

29 Dec 2024

30 Dec 2024

31 Dec 2024


## Delta Lake connector

* Improve performance of reading from Delta Lake tables by compressing files
Copy link
Member Author

Choose a reason for hiding this comment

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

@raunaqmorarka .. how does this work with existing stuff. I assume the files are unmodified as usual so it only applies to new data .. so reading is NOT accelerated for old data .. only for newly written files that are subsequently read .. and as such.. do we need to reword @martint .. also note I added the info about SNAPPY being the old default.

## Faker connector

* Add support for views. ({issue}`24242`)
* Replace predicate pushdown with `min`, `max`, and `options` column properties. ({issue}`24147`)
Copy link
Member Author

@mosabua mosabua Dec 28, 2024

Choose a reason for hiding this comment

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

I think we probaly want to just remove the mention of predicate pushdown and mention addition of the column properties and what they add. Sounds ok @raunaqmorarka and @nineinchnick ?

Copy link
Member

Choose a reason for hiding this comment

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

It's breaking change, so we should definitely say that predicate pushdown are not supported anymore.


## Faker connector

* Add support for views. ({issue}`24242`)
Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks for adding the docs entry for the SQL support section. Question though .. do we need to add more specific info like .. where are those views stored? Do they survive a cluster restart?

Copy link
Member Author

@mosabua mosabua Dec 28, 2024

Choose a reason for hiding this comment

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

And are create, drop, and alter supported?

Copy link
Member

Choose a reason for hiding this comment

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

The implementation is copied from the memory connector. The views are stored in memory, same as the tables are, and we only mention this for tables. There are tests that prove we support CREATE VIEW, DROP VIEW and ALTER VIEW statements.

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.

2 participants