docs/src/main/sphinx/release/release-0.206.md
dictionary_aggregation is enabled.GROUP BY, but the cardinality of the
grouping columns is one. For example: SELECT c1, sum(c2) FROM t WHERE c1 = 'foo' GROUP BY c1ST_Union, {func}ST_Geometries, {func}ST_PointN, {func}ST_InteriorRings,
and {func}ST_InteriorRingN geospatial functions.split_to_multimap function.approx_distinct function to support the following types:
INTEGER, SMALLINT, TINYINT, DECIMAL, REAL, DATE,
TIMESTAMP, TIMESTAMP WITH TIME ZONE, TIME, TIME WITH TIME ZONE, IPADDRESS.system.runtime.queries table.ORDER BY without LIMIT in a distributed manner.
This can be disabled with the distributed-sort configuration property
or the distributed_sort session property.VARCHAR(n) to CHAR(n), and remove implicit coercion the other way around.
As a result, comparing a CHAR with a VARCHAR will now follow
trailing space insensitive CHAR comparison semantics.TIMESTAMP (aka TIMESTAMP WITHOUT TIME ZONE) type,
TIME (aka TIME WITHOUT TIME ZONE) type, and TIME WITH TIME ZONE type.
The legacy behavior remains default.
At this time, it is not recommended to enable the new semantics.
For any connector that supports temporal types, code changes are required before the connector
can work correctly with the new semantics. No connectors have been updated yet.
In addition, the new semantics are not yet stable as more breaking changes are planned,
particularly around the TIME WITH TIME ZONE type.applicationNamePrefix parameter, which is combined with
the ApplicationName property to construct the client source name.skip.footer.line.count and skip.header.line.count
when using HDFS authentication with Kerberos.