Release 0.206
Fix planning failure when a query contains a
GROUP BY
, but the cardinality of the grouping columns is one. For example:SELECT c1, sum(c2) FROM t WHERE c1 = 'foo' GROUP BY c1
Add
ST_Union()
, ST_Geometries(), , ST_InteriorRings(), and geospatial functions.Add split_to_multimap() function.
Add a resource group ID column to the
system.runtime.queries
table.Add support for executing
ORDER BY
withoutLIMIT
in a distributed manner. This can be disabled with thedistributed-sort
configuration property or thedistributed_sort
session property.Improve query cost estimation by only including non-null rows when computing average row size.
Add new semantics that conform to the SQL standard for temporal types. It affects the
TIMESTAMP
(akaTIMESTAMP WITHOUT TIME ZONE
) type,TIME
(akaTIME WITHOUT TIME ZONE
) type, andTIME 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 theTIME WITH TIME ZONE
type.
- Add
applicationNamePrefix
parameter, which is combined with theApplicationName
property to construct the client source name.
Reduce ORC reader memory usage by reducing unnecessarily large internal buffers.
Add support for case-insensitive column lookup for Parquet readers.