Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Download | Release Notes | Changelog |
Release date: 9 Nov 2016
MariaDB Connector/J 1.5.5 is a Stable (GA) release.
This version is a bug-fix release.
: Disabling useBatchMultiSend option for Aurora, since can hang connection.
: Store procedure with resultSet get wrong getUpdateCount() value (0 in place of -1)
: permit OldAuthSwitchRequest protocol (compatibility with 5.5 server using plugin)
: Client sockets remain when server close socket on connection (when server maximum connections number has been reached)
: Metadata getProcedureColumns precision's information corrected for date/timestamp/datetime
: Metadata TINYTEXT type return Types.LONGVARCHAR instead of Types.VARCHAR
: Maxscale compatibility : Permit protocol compression only if server permit it
: Load data infile with large files fails with OutOfMemoryError correction
: use KeyStore default property when not using keyStore option
: Encoding on clob column when useServerPrepStmts=true correction
: fix a possible race condition MariaDbPooledConnection
Release Notes for the MariaDB Connector/J 1.5 series
CONJ-423 : Permit having the MySQL driver and MariaDB driver in the same classpath
CONJ-431 : multi-values queries return only one generated key
CONJ-437 : ResultSet.getString on field with ZEROFILL doesn't have the '0' leading char when using binary protocol
CONJ-435 : avoid "All pipe instances are busy" exception on multiple connections to the same named pipe
: ResultSet first() throws an exception for scroll type if TYPE_FORWARD_ONLY, only when streaming
: handle very big blob (1Gb)
: 1.5.8 regression : ResultSet returns duplicate entries when using fetchsize
: ResultSet.getDouble/getFloat may throw a NumberFormatException
: using option rewriteBatchedStatements permits rewrite when a query has a column/table that contains the 'select' keyword
CONJ-212 : Implement password encoding charset option to permit connecting using a password created with a connection that had a different charset
CONJ-399 : resultSet getLong() for BIGINT column fails if value is Long.MIN_VALUE in Text protocol
CONJ-395 : Aurora does not randomise selection of read replicas
CONJ-392 : Aurora cluster endpoint detection timezone issue
CONJ-394 : mysql_native_password plugin authentication fail when default-auth set
: handle timestamp '0000-00-00 00:00:00' getString()
: Use SELECT in place of SHOW command on connection
: revised implementation for handling multiple resultSet correctly for a unique command (was failing if more than 2)
CONJ-380 : continous integration now test against maxscale
Download | Release Notes | Changelog |
Release date: 13 Jan 2017
MariaDB Connector/J 1.5.7 is a Stable (GA) release.
This version is a bug-fix release.
: handling failover when packet > max_allowed_packet reset the connection state.
: possible NPE on ResultSet.close() correction
: Calendar instance not cleared before being used in ResultSet.getTimestamp
Download | Release Notes | Changelog |
Release date: 15 Feb 2017
MariaDB Connector/J 1.5.8 is a Stable (GA) release.
This version is a bug-fix release.
: getGeneratedKeys() on table without generated key failed on second execution
: Metadata take in account tinyInt1isBit in method columnTypeClause
: ResultSet.last() isLast() afterLast() and isAfterLast() correction when streaming
: ResultSet.absolute() should not always return true
Download | Release Notes | Changelog |
Release date: 13 Oct 2016
MariaDB Connector/J 1.5.4 is a Stable (GA) release.
This version is a bug-fix release.
: Connection.getClientInfo implementation correction to follow JDBC rules
: PrepareStatement setString() with empty string correction.
: replacing ManagementFactory.getRuntimeMXBean() that cause Connection timeout issue due to DNS lookup depending on environment
: Metadata getColumns(...) resultSet doesnt have "IS_GENERATEDCOLUMN" info
CONJ-392 : Aurora cluster endpoint detection fails when time_zone doesn't match system_time_zone
CONJ-425 : CallableStatement getObject class according to java.sql.Types value
CONJ-426 : Allow executeBatch to be interrupted
CONJ-420 : High CPU usage against Aurora after 2 hours inactivity
CONJ-358 : Permit using private key with password that differs from keyStore password
CONJ-356 : secure connection : use KeyStore private key and associate public keys certificates only
CONJ-342 : Empty clientCertificateKeyStoreUrl option correction
CONJ-353 : IBM jdk compatibility issue
CONJ-354 : Streaming issue when using procedures in PrepareStatement/Statement
CONJ-345 : Regression with using COLLATE keyword in PrepareStatement query
CONJ-352 : metadata correction on getPrecision() for numeric fields
CONJ-350 : make prepare fallback to client prepare if query cannot be prepare
New Option :
Some options which names where confusing have been renamed (the old names still works):
clientCertificateKeyStoreUrl
keyStore
like system property "javax.net.ssl.keyStore"
clientCertificateKeyStorePassword
keyStorePassword
like system property "javax.net.ssl.keyStorePassword"
trustCertificateKeyStoreUrl
trustStore
like system property "javax.net.ssl.trustStore"
trustCertificateKeyStorePassword
trustStorePassword
Download | Release Notes | Changelog |
Release date: 16 Aug 2016
MariaDB Connector/J 1.5.1 is a Release candidate (RC) release.
Aurora host auto-discovery ()
Aurora now auto discovers nodes from the cluster endpoint.
Aurora endpoints
Every aurora instance has a specific endpoint, i.e. a URL that identifies the
host. These endpoints look like xxx.yyy.zzz.rds.amazonaws.com.
There is another endpoint named "cluster endpoint" (formatxxx.cluster-yyy.zzz.rds.amazonaws.com) which is assigned to the current
master instance and will change when a new master is promoted.
In previous versions, cluster endpoint use was discouraged, since, when a failover occurs, this cluster endpoint can point for a limited time to a host that is no longer the current master. Old recommendation was to list all specific end-points, like:
This kind of URL string will still work, but now the recommended URL string has to use only the cluster endpoint:
The driver will automatically discover master and slaves of this cluster from the current cluster endpoint during connection time. This permits adding new replicas to the cluster instance that will be discovered without changing the driver configuration.
This discovery appends at connection time, so if you are using a pool framework, check if this framework has a property that controls the maximum lifetime of a connection in the pool, and set a value to avoid infinite lifetime. When this lifetime is reached, pool will discarded for the current connection, and will create a new one (if needed). New connections will use the new replicas.
(If connections are never discarded, new replicas will begin to be used only when a failover occurs.)
and : rewriteBatchedStatements execute single query exceptions correction.
For a list of all changes made in this release, with links to detailed information on each push, see the .
like system property "javax.net.ssl.trustStorePassword"
jdbc:mysql:aurora://a.yyy.zzz.rds.amazonaws.com.com,b.yyy.zzz.rds.amazonaws.com.com/dbjdbc:mysql:aurora://xxx.cluster-yyy.zzz.rds.amazonaws.com/dbDownload | Release Notes | Changelog |
Release date: 1 Sep 2016
MariaDB Connector/J 1.5.2 is a Stable (GA) release.
This version is a feature release.
.
kerberos implementation on windows has java limitations. Main limitations are :
need a windows registry entry (HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters\AllowTGTSessionKey) so windows shared current ticket to java.
java kinit must be executed to create a Ticket.
restriction when client with local admin rights
See for more informations
Kerberos GSSAPI implementation on windows in now based on that support windows SSPI based on . If waffle-jna (and dependencies) is on classpath, native implementation will automatically be used.
This removes all those limitations.
/
Driver before version 1.5 support only TLSv1. Default supported protocol are now TLSv1 and TLSv1.1, other protocols can be activated by options.
MariaDB and MySQL community server permit TLSv1 and TLSv1.1. MariaDB server from version 10.0.15 is using the openSSL library permitting TLSv1.2 (>= 5.5.41 for the 5.5 branch).YaSSL doesn't support TLSv1.2, so if MariaDB server is build from sources with YaSSL, only TLSv1 and TLSv1.1 will be available, even for versions > 10.0.15
TLSv1.2 can be enabled by setting option enabledSslProtocolSuites to values "TLSv1, TLSv1.1, TLSv1.2".
A new option enabledSslCipherSuites permits setting a specific cipher.
New Options :
Different performance improvements have been implemented :
Using PreparedStatement on client side uses a simple query parser to identify query parameters. This parsing was taking up to 7% of query time, reduced to 3%.
Better UTF-8 decoding avoiding memory consumption and gaining 1-2% query time for big String.
client parsing optimization : rewriteBatchedStatements (insert into ab (i) values (1) and insert into ab (i) values (2) rewritten as insert into ab (i) values (1), (2))
is now 19% faster (Depending on queries 40-50% of CPU time was spent testing that the buffer size was big enough to contain the query)
Batch improvement : Send X command without reading results, and read those X results asynchronously. Basically that permits avoiding a lot of 'ping-pong' between driver and server.
New Options :
When using MySQL/MariaDB prepared statements, there are 3 exchanges with server :
PREPARE - Prepares statement for execution.
EXECUTE - Executes a prepared statement preparing by a PREPARE statement.
DEALLOCATE PREPARE - Releases a prepared statement.
See for more information.
Since , the last PREPARE statement id can be identified with value "-1". The driver uses this functionality to PREPARE and EXECUTE in one client-server round-trip.
Client logging can be enabled, permitting logging of query information, execution time and different failover information. This implementation needs the standard SLF4J dependency.
New Options :
()
Aurora now auto discovers nodes from the cluster endpoint.
Aurora endpoints
Every aurora instance has a specific endpoint, i.e. a URL that identifies the
host. These endpoints look like xxx.yyy.zzz.rds.amazonaws.com.
There is another endpoint named "cluster endpoint" (formatxxx.cluster-yyy.zzz.rds.amazonaws.com) which is assigned to the current
master instance and will change when a new master is promoted.
In previous versions, cluster endpoint use was discouraged, since, when a failover occurs, this cluster endpoint can point for a limited time to a host that is no longer the current master. The old recommendation was to list all specific end-points, like:
This kind of URL string will still work, but now the recommended URL string only has to use the cluster endpoint:
The driver will automatically discover master and slaves of this cluster from the current cluster endpoint during connection time. This permits adding new replicas to the cluster instance that will be discovered without changing the driver configuration.
This discovery appends at connection time, so if you are using a pool framework, check if this framework has a property that controls the maximum lifetime of a connection in the pool, and set a value to avoid infinite lifetime. When this lifetime is reached, the pool will discarded for the current connection, and will create a new one (if needed). New connections will use the new replicas.
(If connections are never discarded, new replicas will begin to be used only when a failover occurs.)
LOAD DATA INFILE The fastest way to load most data is using the query . The problem is using "LOAD DATA LOCAL INFILE" (ie : loading a file from client), may be a security problem :
A "man in the middle" proxy server can change the actual file asked from server so client will send a Local file to this proxy.
If someone has can execute a query from the client, he can have access to any file on client (according to the rights of the user running the client process).
See the for more information.
Interceptors can now filter the LOAD DATA LOCAL INFILE query's file location to validate the path and file name. Those interceptors:
Must implement interface org.mariadb.jdbc.LocalInfileInterceptor.
Use implementation, so interceptors classes must be listed in file META-INF/services/org.mariadb.jdbc.LocalInfileInterceptor.
Example:
file META-INF/services/org.mariadb.jdbc.LocalInfileInterceptor must exist with content org.project.LocalInfileInterceptorImpl.
You can get rid of defining the META-INF/services file using the framework, which allows using the annotation @AutoService(LocalInfileInterceptor.class) that will register the implementation as a service automatically.
Using the previous example:
: Add jdbc nString, nCharacterStream, nClob implementation
: Wrong Exception thrown for ScrollType TYPE_SCROLL_INSENSITIVE
: Error on Callable function exception when no parameter and space before parenthesis
: Permit using Call with Statement / Prepare Statement
and : rewriteBatchedStatements execute single query exceptions correction.
RC corrections
: Pool connection may fail to connect with good user
: option enabledSslCipherSuites rely on java supportedCipherSuites (replacing enabledCipherSuites)
UTF-8 conversion correction (last character was not well encode if high surrogate)
For a list of all changes made in this release, with links to detailed information on each push, see the Connector/J 1.5.x changelogs:
there was some memory wastage when a query returned a big resultset (> 10kb), slowing the query
and many more
profileSql
log connection id, query and execution time.log example : 2016-07-29 23:28:50 [main] INFO org.mariadb.jdbc.MariaDbStatement - Query - conn:10295 - 0,309 ms - "select * from TABLE"Default: false. Since 1.5.0
CONJ-331 : clearWarnings() now throw exception on closed connection
CONJ-299 : PreparedStatement.setObject(Type.BIT, "1") registered as true.
CONJ-293 : permit named pipe connection without host
CONJ-333 : ResultSet.getString() of PreparedStatement return NULL When TIME column value=00:00:00
enabledSslProtocolSuites
Force TLS/SSL protocol to a specific set of TLS versions (comma separated list). Example : "TLSv1, TLSv1.1, TLSv1.2" Default: TLSv1, TLSv1.1. Since 1.5.0
enabledSslCipherSuites
Force TLS/SSL cipher (comma separated list). Example : "TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384" Default: use JRE ciphers. Since 1.5.0
useBatchMultiSend
PreparedStatement.executeBatch() will send many QUERY before reading result packets.Default: true. Since 1.5.0
useBatchMultiSendNumber
When using useBatchMultiSend, indicate maximum query that can be send at a time.Default: 100. Since 1.5.0
log
Enable log information. require Slf4j version > 1.4 dependency.Default: false. Since 1.5.0
maxQuerySizeToLog
Only the first characters corresponding to this options size will be displayed in logsDefault: 1024. Since 1.5.0
slowQueryThresholdNanos
Will log query with execution time superior to this value (if defined )Default: 1024. Since 1.5.0
kerberos implementation on windows has java limitations. Main limitations are :
need a windows registry entry (HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters\AllowTGTSessionKey) so windows shared current ticket to java.
java kinit must be executed to create a Ticket.
restriction when client with local admin rights
See see openJDK issue for more informations
Kerberos GSSAPI implementation on windows in now based on Waffle that support windows SSPI based on JNA. If waffle-jna (and dependencies) is on classpath, native implementation will automatically be used.
This removes all those limitations.
Driver before version 1.5 support only TLSv1. Default supported protocol are now TLSv1 and TLSv1.1, other protocols can be activated by options.
MariaDB and MySQL community server permit TLSv1 and TLSv1.1. MariaDB server from version 10.0.15 is using the openSSL library permitting TLSv1.2 (>= 5.5.41 for the 5.5 branch).YaSSL doesn't support TLSv1.2, so if MariaDB server is build from sources with YaSSL, only TLSv1 and TLSv1.1 will be available, even for version > 10.0.15
TLSv1.2 can be enabled by setting option enabledSslProtocolSuites to values "TLSv1, TLSv1.1, TLSv1.2".
A new option enabledSslCipherSuites permit to set specific cipher.
New Options :
enabledSslProtocolSuites
Force TLS/SSL protocol to a specific set of TLS versions (comma separated list). Example : "TLSv1, TLSv1.1, TLSv1.2"Default: TLSv1, TLSv1.1. Since 1.5.0
enabledSslCipherSuites
Force TLS/SSL cipher (comma separated list). Example : "TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384"Default: use JRE ciphers. Since 1.5.0
Different performance improvement have been done :
Using PreparedStatement on client side use a simple query parser to identify query parameters. This parsing was taking up to 7% of query time, reduced to 3%.
Better UTF-8 decoding avoiding memory consumption and gain 1-2% query time for big String.
client parsing optimization : rewriteBatchedStatements (insert into ab (i) values (1) and insert into ab (i) values (2) rewritten as insert into ab (i) values (1), (2)) is now 19% faster (Depending on queries 40-50% of CPU time was spend testing that buffer size is big enough to contain query).
there was some memory wastage when query return big resultset (> 10kb), slowing query.
and a lot more
CONJ-320 Batch improvement : Send X command without reading results, and read those X results asynchronously . Basically that permit to avoid a lot of 'ping-pong' between driver and server.
New Options :
useBatchMultiSend
PreparedStatement.executeBatch() will send many QUERY before reading result packets.Default: true. Since 1.5.0
useBatchMultiSendNumber
When using useBatchMultiSend, indicate maximum query that can be send at a time.Default: 100. Since 1.5.0
When using MySQL/MariaDB prepared statement, there will be 3 exchanges with server :
PREPARE - Prepares statement for execution.
EXECUTE - Executes a prepared statement preparing by a PREPARE statement.
DEALLOCATE PREPARE - Releases a prepared statement.
See for more information.
Since MariaDB 10.2.2, last PREPARE statement id can be identified with value "-1". Driver is using this functionality to PREPARE and EXECUTE in one client-server round-trip.
Client logging can be enable, permitting to log query information, execution time and different failover informations. This implementation need the standard SLF4J dependency.
New Options :
log
Enable log information. require Slf4j version > 1.4 dependency.Default: false. Since 1.5.0
maxQuerySizeToLog
Only the first characters corresponding to this options size will be displayed in logsDefault: 1024. Since 1.5.0
slowQueryThresholdNanos
Will log query with execution time superior to this value (if defined )Default: 1024. Since 1.5.0
CONJ-305 LOAD DATA INFILE The fastest way to load many datas is using query . Problem is using "LOAD DATA LOCAL INFILE" (ie : loading a file from client), may be a security problem :
A "man in the middle" proxy server can change the actual file asked from server so client will send a Local file to this proxy.
If someone has can execute query from client, he can have access to any file on client (according to the rights of the user running the client process).
See for more information.
Interceptors can now filter LOAD DATA LOCAL INFILE query's file location to validate path / file name. Those interceptors:
Must implement interface org.mariadb.jdbc.LocalInfileInterceptor.
Use ServiceLoader implementation, so interceptors classes must be listed in file META-INF/services/org.mariadb.jdbc.LocalInfileInterceptor.
Example:
file META-INF/services/org.mariadb.jdbc.LocalInfileInterceptor must exist with content org.project.LocalInfileInterceptorImpl.
You can get ride of defining the META-INF/services file using google auto-service framework, permitting to use annotation @AutoService(LocalInfileInterceptor.class) that will register the implementation as a service automatically.
Using the previous example:
CONJ-260 : Add jdbc nString, nCharacterStream, nClob implementation
For a list of all changes made in this release, with links to detailed information on each push, see the changelog.
jdbc:mysql:aurora://a.yyy.zzz.rds.amazonaws.com.com,b.yyy.zzz.rds.amazonaws.com.com/dbjdbc:mysql:aurora://xxx.cluster-yyy.zzz.rds.amazonaws.com/dbpackage org.project;
public class LocalInfileInterceptorImpl implements LocalInfileInterceptor {
@Override
public boolean validate(String fileName) {
File file = new File(fileName);
String absolutePath = file.getAbsolutePath();
String filePath = absolutePath.substring(0,absolutePath.lastIndexOf(File.separator));
return filePath.equals("/var/tmp/exchanges");
}
}@AutoService(LocalInfileInterceptor.class)
public class LocalInfileInterceptorImpl implements LocalInfileInterceptor {
@Override
public boolean validate(String fileName) {
File file = new File(fileName);
String absolutePath = file.getAbsolutePath();
String filePath = absolutePath.substring(0,absolutePath.lastIndexOf(File.separator));
return filePath.equals("/var/tmp/exchanges");
}
}package org.project;
public class LocalInfileInterceptorImpl implements LocalInfileInterceptor {
@Override
public boolean validate(String fileName) {
File file = new File(fileName);
String absolutePath = file.getAbsolutePath();
String filePath = absolutePath.substring(0,absolutePath.lastIndexOf(File.separator));
return filePath.equals("/var/tmp/exchanges");
}
}@AutoService(LocalInfileInterceptor.class)
public class LocalInfileInterceptorImpl implements LocalInfileInterceptor {
@Override
public boolean validate(String fileName) {
File file = new File(fileName);
String absolutePath = file.getAbsolutePath();
String filePath = absolutePath.substring(0,absolutePath.lastIndexOf(File.separator));
return filePath.equals("/var/tmp/exchanges");
}
}profileSql
log connection id, query and execution time.log example : 2016-07-29 23:28:50 [main] INFO org.mariadb.jdbc.MariaDbStatement - Query - conn:10295 - 0,309 ms - "select * from TABLE"Default: false. Since 1.5.0
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.
This page is: Copyright © 2025 MariaDB. All rights reserved.