Add Trino 398 release notes #14319
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,63 @@ | ||
| # Release 398 (28 Sep 2022) | ||
|
|
||
| ## General | ||
|
|
||
| * Add Hudi connector. ({issue}`10228`) | ||
|
colebow marked this conversation as resolved.
Outdated
|
||
| * Add metrics for the execution time of filters and projections to `EXPLAIN | ||
| ANALYZE VERBOSE`. ({issue}`14135`) | ||
| * Show local cost estimates when using `EXPLAIN`. ({issue}`14268`) | ||
| * Fix timeouts happening too early because of improper handling of the | ||
| `node-scheduler.allowed-no-matching-node-period` configuration property. ({issue}`14256`) | ||
| * Fix query failure for `MERGE` queries when `task_writer_count` is greater | ||
| than one. ({issue}`14306`) | ||
|
|
||
| ## Accumulo connector | ||
|
|
||
| * Add support for column comments when creating a new table. ({issue}`14114`) | ||
| * Move column mapping and index information into the output of `DESCRIBE` | ||
| instead of a comment. ({issue}`14095`) | ||
|
|
||
| ## BigQuery connector | ||
|
|
||
| * Fix improper escaping of backslash and newline characters. ({issue}`14254`) | ||
| * Fix query failure when the predicate involves a `varchar` value with a | ||
| backslash. ({issue}`14254`) | ||
|
|
||
| ## ClickHouse connector | ||
|
|
||
| * Upgrade minimum required Clickhouse version to 21.8. ({issue}`14112`) | ||
|
|
||
| ## Delta Lake connector | ||
|
|
||
| * Improve performance when reading Parquet files for queries with predicates. ({issue}`14247`) | ||
|
|
||
| ## Elasticsearch connector | ||
|
|
||
| * Deprecate support for query pass-through using the special | ||
| `<index>$query:<es-query>` dynamic tables in favor of the `raw_query` table | ||
| function. Legacy behavior can be re-enabled with the | ||
| `elasticsearch.legacy-pass-through-query.enabled` configuration property. ({issue}`14015`) | ||
|
|
||
| ## Hive connector | ||
|
|
||
| * Add support for partitioned views when legacy mode for view translation is | ||
| enabled. ({issue}`14028`) | ||
| * Extend the `flush_metadata_cache` procedure to be able to flush table-related | ||
| caches instead of only partition-related caches. ({issue}`14219`) | ||
| * Improve performance when reading Parquet files for queries with predicates. ({issue}`14247`) | ||
|
|
||
| ## Iceberg connector | ||
|
|
||
| * Improve performance when reading Parquet files for queries with predicates. ({issue}`14247`) | ||
| * Fix potential table corruption when changing a table before it is known if | ||
| committing to the Glue metastore has failed or succeeded. ({issue}`14174`) | ||
|
Comment on lines
+52
to
+53
Member
There was a problem hiding this comment. Where does
Member
Author
There was a problem hiding this comment. If we know that committing to the Hive metastore has succeeded, then there is no corruption. So this error would only happen while it is unclear, aka before we know.
Member
There was a problem hiding this comment. Maybe i just can't read release notes -- i am not english native after all -- but i really don't get the use of "before" here.
Member
There was a problem hiding this comment. The language in the proposed RN at #14154 (comment) is much clearer to me as well. The only nit would be |
||
|
|
||
| ## Pinot connector | ||
|
|
||
| * Add support for the `timestamp` type. ({issue}`10199`) | ||
|
|
||
| ## SPI | ||
|
|
||
| * Extend `ConnectorMetadata.getStatisticsCollectionMetadata` to allow the | ||
| connector to request the computation of any aggregation function during stats | ||
| collection. ({issue}`14233`) | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Thanks for responding to #14194 (comment)
I still don't think the wording conveys the meaning. "changing a table before" sounds like there is some kind of a race condition in play, where it's not the case