Fix variable resolution when lambda argument has the same name as a table column.
Improve error message when running SHOWTABLES on a catalog that does not exist.
Improve performance for queries with highly selective filters.
Execute USE on the server rather than in the CLI, allowing it
to be supported by any client. This requires clients to add support for
the protocol changes (otherwise the statement will be silently ignored).
Allow casting JSON to ROW even if the JSON does not contain every
field in the ROW.
Add support for dereferencing row fields in lambda expressions.
Support configuring multiple authentication types, which allows supporting
clients that have different authentication requirements or gracefully
migrating between authentication types without needing to update all clients
at once. Specify multiple values for http-server.authentication.type,
separated with commas.
Add support for TLS client certificates as an authentication mechanism by
specifying CERTIFICATE for http-server.authentication.type.
The distinguished name from the validated certificate will be provided as a
javax.security.auth.x500.X500Principal. The certificate authority (CA)
used to sign client certificates will be need to be added to the HTTP server
KeyStore (should technically be a TrustStore but separating them out is not
Skip sending final leg of SPNEGO authentication when using Kerberos.
Per the JDBC specification, close the ResultSet when Statement is closed.
Add support for TLS client certificate authentication by configuring the
SSLKeyStorePath and SSLKeyStorePassword parameters.
Add support for transactions using SQL statements or the standard JDBC mechanism.
Allow executing the USE statement. Note that this is primarily useful when
running arbitrary SQL on behalf of users. For programmatic use, continuing
to use setCatalog() and setSchema() on Connection is recommended.