Release 0.75
The Hive connector now supports renaming tables. By default, this feature is not enabled. To enable it, set
hive.allow-rename-table=true
in your Hive catalog properties file.
General Changes
Optimize with a constant to execute as the much faster
count(*)
Add support for binary types to the JDBC driver
The legacy byte code compiler has been removed
New aggregation framework (~10% faster)
Added max_by() aggregation function
Fixed cross join planning error for certain query shapes
Added hex and base64 conversion functions for varbinary
Fix the
LIKE
operator to correctly match against values that contain multiple lines. Previously, it would stop matching at the first newline.Add support for renaming tables using the statement.
Add basic support for inserting data using the INSERT statement. This is currently only supported for the Raptor connector.
The and json_extract_scalar() functions now support the square bracket syntax:
As part of this change, the set of characters allowed in a non-bracketed path segment has been restricted to alphanumeric, underscores and colons. Additionally, colons cannot be used in a un-quoted bracketed path segment. Use the new bracket syntax with quotes to match elements that contain special characters.
Scheduler Changes
Queries that use the row_number() function are substantially faster and can run on larger result sets for two types of queries.
Performing a partitioned limit that choses N
arbitrary rows per partition is a streaming operation. The following query selects five arbitrary rows from orders
for each orderstatus
:
Performing a partitioned top-N that chooses the maximum or minimum N
rows from each partition now uses significantly less memory. The following query selects the five oldest rows based on orderdate
from orders
for each orderstatus
:
Use the statement to see if any of these optimizations have been applied to your query.
SPI Changes
The core Presto engine no longer automatically adds a column for count(*)
queries. Instead, the will receive an empty list of column handles.
The Type
and Block
APIs have gone through a major refactoring in this release. The main focus of the refactoring was to consolidate all type specific encoding logic in the type itself, which makes types much easier to implement. You should consider Type
and Block
to be a beta API as we expect further changes in the near future.
To simplify the API, ConnectorOutputHandleResolver
has been merged into ConnectorHandleResolver
. Additionally, ConnectorHandleResolver
, ConnectorRecordSinkProvider
and ConnectorMetadata
were modified to support inserts.
This is a backwards incompatible change with the previous connector and type SPI, so if you have written a connector or type, you will need to update your code before deploying this release. In particular, make sure your connector can handle an empty column handles list (this can be verified by running on a table from your connector).