Add Trino 478 release notes #27089
Add Trino 478 release notes #27089
Conversation
Co-authored-by: Mateusz "Serafin" Gajewski <[email protected]>
Co-Authored-By: Cole Bowden <[email protected]>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
| * Fix potential incorrect results when reading `row` type. ({issue}`26806`) | ||
| * Return all catalogs, including uninitialized ones, for queries from `metadata.catalogs`. ({issue}`26918`) | ||
| * Ensure that queries with and without `EXPLAIN ANALYZE` are planned identically. ({issue}`26938`) | ||
| * In row pattern matching, restrict logical navigations to current match in running semantics. ({issue}`26981`) |
There was a problem hiding this comment.
from @losipiuk (#26726 (comment)):
The nomenclature here is technical. Does it match what we us in docs?
|
draft until https://github.com/trinodb/trino/pull/27089/files#r2459921217 i cannot 'request changes' on a PR that I opened, treat draft status as meaning just that |
| policies can be selected by the user. ({issue}`26628`) | ||
| * Add support for loading plugins from multiple directories. ({issue}`26855`) | ||
| * Add the `/v1/integrations/gateway` endpoint for integration with Trino Gateway. ({issue}`26548`) | ||
| * Allow dropping an uninitialized catalog that failed to load. ({issue}`26918`) |
There was a problem hiding this comment.
do we want to quantify this with "When using dynamic catalogs" or similar?
* When using dynamic catalogs, allow dropping ...
There was a problem hiding this comment.
What's an "uninitialized catalog"?
There was a problem hiding this comment.
Then the "that failed to load" part is redundant. I would just say:
* Allow dropping catalogs that failed to load correctly.
This comment was marked as duplicate.
This comment was marked as duplicate.
Sorry, something went wrong.
| policies can be selected by the user. ({issue}`26628`) | ||
| * Add support for loading plugins from multiple directories. ({issue}`26855`) | ||
| * Add the `/v1/integrations/gateway` endpoint for integration with Trino Gateway. ({issue}`26548`) | ||
| * Allow dropping an uninitialized catalog that failed to load. ({issue}`26918`) |
There was a problem hiding this comment.
What's an "uninitialized catalog"?
| * Return all catalogs, including uninitialized ones, for queries from `metadata.catalogs`. ({issue}`26918`) | ||
| * Fix `EXPLAIN ANALYZE` planning so that it executes with the same plan as would be used to execute the query | ||
| being analyzed. ({issue}`26938`) | ||
| * Fix row pattern matching logical navigations in running semantics to be always constraint to current match. |
There was a problem hiding this comment.
This is too technical. What's the effect of "returning a position outside the current match"? What's the user-visible behavior?
|
|
||
| ## Delta Lake connector | ||
|
|
||
| * Fix failure when reading `map` type with `json` value type when a value is `NULL`. ({issue}`26700`) |
There was a problem hiding this comment.
This is still not clear to me. Does "map type" refer to Delta Lake's type? Does "json value type" refer to Trino's type?
There was a problem hiding this comment.
fwiw, originally PR had this
Fix reading
nullmap withVARIANTas value type.
i believe "json value type" refers to Trino's type
There was a problem hiding this comment.
The map type also refers to Trino type in my understanding. The PR contains a below test:
MAP(ARRAY['key1'], ARRAY[NULL])The column type is map(varchar, json).
| * Add support for reading encrypted Parquet files. ({issue}`24517`, {issue}`9383`) | ||
| * Deprecate the `gcs.use-access-token` configuration property. Use `gcs.auth-type` instead. ({issue}`26681`) | ||
| * Improve performance of queries using complex predicates on `$path` column. ({issue}`27000`) | ||
| * Fix writing invalid dates and timestamps before `1582-10-15` when writing ORC files by setting calendar type |
There was a problem hiding this comment.
The "by setting calendar type ..." part is unnecessary. If someone wants to know the implementation details, they can look at the PR.
So, simplify it to:
* Fix writing invalid dates and timestamps before `1582-10-15` when writing ORC data.
There was a problem hiding this comment.
i think the important part is that trino was reading that data back correctly (or as-if correctly), and some other systems were not. did you omit this part intentionally, @martint ?
There was a problem hiding this comment.
Fair enough. We can extend it with:
* Fix writing invalid dates and timestamps before `1582-10-15` in ORC data, which could affect correctness when reading them in other query engines such as Apache Hive.
|
Added newer entries since Oct 23. |
6 participants
Release notes for the upcoming Trino 478 release.
Summary by Sourcery
Add documentation for Trino 478 release notes and include it in the release notes index
Documentation: