presto-docs/src/main/sphinx/release/release-0.219.rst
LIMIT on top of a FULL OUTER JOIN.SMALLINT and TINYINT types.$bucket filter.ANALYZE statement for a given connector would remain in the system.metadata.analyze_properties table
even after the connector was removed.!ST_Length for SphericalGeography type..view_owner column to the information_schema.views system table.JSON version of the query plan to QueryCompletedEvent.current_role reserved word as an identifier.!split function.
When an empty string is used as the delimiter, the string will be split into individual characters.raptor.minimum-node-count configuration property. If the number of nodes in a cluster is less than the configured value,
data recovery and reassignment will not run.raptor.startup-grace-period configuration property to specify the delay for the initial bucket balancer run after the coordinator startup.hive.ignore-table-bucketing configuration property and ignore_table_bucketing session property.
When set to true, these properties enable reading from partitions whose bucketing scheme does not match the table bucketing scheme.INSERT queries were not run when there was a result mismatch.INSERT query verification.query_max_execution_time session property.expected-double-precision with relative-error-margin.!array_sort before :func:!checksum.SELECT queries by rewriting SELECT queries as CREATE TABLE AS and using checksum queries to verify the results.
This eliminates the row count limit for SELECT queries.presto.max-attempts, presto.min-backoff-delay,
presto.max-backoff-delay, presto.backoff-scale-factor. Similar configurations prefixed with cluster-connection instead of presto
are introduced for retrying transient network failures when communicating with the coordinator. Intermediate failures are recorded and emitted in the output.metadata-timeout and checksum-timeout to set the timeouts for metadata queries
(i.e., describe queries that read table schema) and checksum queries.source-query.table-name configuration property to specify the name of the MySQL table from which the verifier queries will loaded.human-readable.log-file to allow human-readable verification results to be logged into the specified file instead of stdout.query-database to source-query.database, suites to source-query.suites,
max_queries to source-query.max-queries-per-suite, event-client to event-clients, event-log-file to json.log-file,
run-id to test-id, thread-count to max-concurrency, control-gateway to control.jdbc_url, test-gateway to test.jdbc_url,
shadow-writes.control-table-prefix to control.table-prefix, and shadow-writes.test-table-prefix to test.table-prefix.control.query-types, test.query-types, source, max-row-count, always-report,
skip-correctness-regex, check-correctness, skip-cpu-check-regex, check-cpu, explain-only, verbose-results-comparison,
quiet, control-teardown-retries, test-teardown-retries, and shadow-writes.RowExpression to SPI, to allow passing resolved expressions to connectors.