Support number accessor methods like ResultSet.getLong() or ResultSet.getDouble()
on decimal values, as well as char or varchar values that can be unambiguously interpreted as numbers. (#5509)
Improve performance of INSERT queries with batch statement. The batch size can be configured via the cassandra.batch-size
configuration property. (#5047)
Add support for ALTER TABLE ... SET AUTHORIZATION SQL syntax to change the table owner. (#5717)
Add support for writing timestamps with microsecond or nanosecond precision, in addition to milliseconds. (#5283)
Export JMX statistics for Glue metastore client request metrics. (#5693)
Collect column statistics during ANALYZE and when data is inserted to table for columns of timestamp(p)
when precision is greater than 3. (#5392)
Improve query performance by adding support for dynamic bucket pruning. (#5634)
Remove deprecated parquet.fail-on-corrupted-statistics (previously known as hive.parquet.fail-on-corrupted-statistics).
A new configuration property, parquet.ignore-statistics, can be used to deal with Parquet files with incorrect metadata. (#3077)
Do not write min/max statistics for timestamp columns. (#5858)
If multiple metastore URIs are defined via hive.metastore.uri, prefer connecting to one which was seen operational most recently.
This prevents query failures when one or more metastores are misbehaving. (#5795)
Fix Hive view access when catalog name is other than hive. (#5785)
Fix failure when the declared length of a varchar(n) column in the partition schema differs from the table schema. (#5484)
Fix Glue metastore pushdown for complex expressions. (#5698)
Remove deprecated parquet.fail-on-corrupted-statistics (previously known as hive.parquet.fail-on-corrupted-statistics).
A new configuration property, parquet.ignore-statistics, can be used to deal with Parquet files with incorrect metadata. (#3077)
Improve performance of queries comparing a timestamp column with a timestamp with time zone constants
for timestamp with time zone precision higher than 3. (#5543)
Improve performance of queries with DISTINCT or LIMIT, or with GROUP BY and no aggregate functions and LIMIT,
when the computation can be pushed down to the underlying database for the PostgreSQL, MySQL, Oracle, Redshift and
SQL Server connectors. (#5522)