Add 352 release notes #6751
Add 352 release notes #6751
Conversation
| * Support user impersonation when using password-based authentication. This is configured | ||
| using `sessionUser` connection URL parameter. Previously user impersonation was possible | ||
| only with other authentication mechanisms. ({issue}`6549`) | ||
| * Add OAuth2 authentication support.({issue}`6576`) |
There was a problem hiding this comment.
Ideally we should have some docs to link to .. but I am not aware of any as of yet.
There was a problem hiding this comment.
I assume this is coming after the release @sopel39 so I am fine with closing this comment
|
|
||
| ## MySQL Connector | ||
|
|
||
| * Improve performance for certain complex queries involving aggregation and predicates (e.g. `HAVING` clause) |
There was a problem hiding this comment.
same applies to a bunch of other entries below .. I know we want to be kind of vague since it does not work for all queries .. but its still kind of weird to say "certain queries". Either remove or replace with "some queries"?
There was a problem hiding this comment.
maybe remove "certain"
it is intentionally vague, as we're not improving all the queries.
By dropping "vague" we would advertise more than we actually deliver
| * Fix query failure when using element of `array(timestamp(p))` in a complex expression | ||
| for `p` greater than 6. ({issue}`6350`) |
| `US/Pacific-New` zone, as it has been removed. ({issue}`6660`) | ||
| * Improve performance of queries using {func}`rank()` window function. ({issue}`6333`) | ||
| * Improve performance of {func}`sum` and {func}`avg` for `decimal` types. ({issue}`6951`) | ||
| * Improve join performance. ({issue}`5981`) |
There was a problem hiding this comment.
Every join, or some particular shapes of it?
There was a problem hiding this comment.
Improve performance of joins where duplicated join output rows can be skipped. I'm not sure if it's not too detailed though.
| * Fix window and streaming aggregation semantics regarding peer rows. Now peer rows are | ||
| not distinct from each other, while previously they had to been equal. ({issue}`6472`) |
There was a problem hiding this comment.
- Should this be "Fix incorrect query results when .." form?
- Also, how a user is gonna know what a streaming aggregation is, or whether they should care?
- As we're talking about "peer rows", this seems applicable to window. Let's split this bullet into two separate things -- window case, talking about peer rows, and [streaming] aggregation case (not talking about peer rows).
| * Support reading timestamp with microsecond or nanosecond precision (as configured with | ||
| `hive.timestamp-precision` property) nested within `array`, `map` or `struct` data types. ({issue}`5195`) |
There was a problem hiding this comment.
We generally support writes too, except for some bugs in Parquet.
Am i correct @jirassimok ?
There was a problem hiding this comment.
We support writes for ORC, RC binary, and RC text (i.e. the formats that have their own writers).
After #6622, we can write in everything except Parquet.
There was a problem hiding this comment.
We support writes for ORC, RC binary, and RC text (i.e. the formats that have their own writers).
@jirassimok but the "hive native" writers work too, right? so we can write to eg a TEXTFILE as well?
After #6622, we can write in everything except Parquet.
That PR is tests-only. So after #6622 we know we can write to anything (except Parquet),
but from user perspective (and so from RNs perspective), we can write even today.
Since that PR is green (or was green earlier), we can declare read/write support already (except Parquet).
There was a problem hiding this comment.
"hive native" writers work too, right?
No, because there are two explicit checks for TIMESTAMP_MILLIS in HiveWriteUtils.
|
|
||
| ## MySQL Connector | ||
|
|
||
| * Improve performance for certain complex queries involving aggregation and predicates (e.g. `HAVING` clause) |
There was a problem hiding this comment.
maybe remove "certain"
it is intentionally vague, as we're not improving all the queries.
By dropping "vague" we would advertise more than we actually deliver
|
|
||
| ## MySQL connector | ||
|
|
||
| * Improve performance for certain complex queries involving aggregation and predicates (e.g. `HAVING` clause) |
There was a problem hiding this comment.
Oh, and 'accidentally' this also adds aggregation pushdown for distinct aggregations, when there is only one aggregation function. So eg count(DISTINCT x) is now pushed down (without or with group by).
| ## Web UI | ||
|
|
||
| * Support JWK with certificate chain for OAuth2 authorization. ({issue}`6428`) | ||
| * Optionally verify JWT audience (`aud`) field for OAuth2 Web UI authentication. ({issue}`6501`) |
There was a problem hiding this comment.
What is optionality driven by? Should we reference config property here?
There was a problem hiding this comment.
Config property is here: http-server.authentication.oauth2.audience, if specified then we require token to have this audience set.
Currently, we are still missing docs for entire feature. We are going to add it soon.
There was a problem hiding this comment.
Same, this doesn't seem specific to web UI
There was a problem hiding this comment.
Ok, I'll move it to a Security section
|
|
||
| * Add OAuth2 authentication. ({issue}`6576`) | ||
| * Support user impersonation when using password-based authentication | ||
| using the new `sessionUser` parameter. ({issue}`6549`) |
| * Optimize cardinality-insensitive aggregations ({func}`max`, {func}`min`, {func}`distinct`, {func}`approx_distinct`) | ||
| over identity partition columns with `optimizer.optimize-metadata-queries` config property | ||
| or `optimize_metadata_queries` session property. ({issue}`5199`) | ||
| * Provide `use_file_size_from_metadata` catalog session property and `iceberg.use-file-size-from-metadata` |
Closes #6502