0.16 Release

Includes dependency updates, notably Threadly 7.0. This increases the minimum JDK version to 11+, but brings in support for JDK 17.

0.15 Release

This release includes the weighted replica improvements from PR #27

0.14 also did not completely release, so instead this release should be used.

0.14 Release

API Breaking changes:

• Fix preferred spelling error for using in setting delegate server choice through .setClientInfo

Improvements included in this release:

• Server weights can be set using the static AuroraClusterMonitor.setHostWeight. This can allow things like different server classes to have load representative to their capabilities. This can make it much safer to have a larger writer and then have the driver provide well sized load on the event of a failover. It can also be used to set weights of 0 to avoid using a server unless there is no other options (perfect for keeping traffic prioritized within an availability zone).
• Dependent library versions updated to the latest

0.13 Release

This release is similar to 0.12, providing more reliability when a replica is an unhealthy state but being unused. It adds additional state setting cases to the connections which it ignores. When the connection is actually used for a query or other server side change then the error will be thrown.

0.12 Release

Includes a fix where a clearWarnings() check on a connection in an error state will throw an exception. Since this is a common operation it may result in an unhealthy cluster member making the connection unusable (despite being able to otherwise defer to other servers).

0.11 Dependency update release

Dependency versions updated per this commit:
34c1c17#diff-503f218d646c10f484fdc9d6315bf2e3

0.10 Cluster stability improvements

Improvements in this release:

• Updated transitive dependencies (mysql -> 8.0.16, threadly -> 5.37)
• Improved javadocs
• Improved cluster state monitoring (see PR #22)

0.9 Release

Changes included in this release:

• More fault tolerance for establishing new connections while the cluster is not fully healthy. Previously a connection must be established to every cluster member for an auroraArc connection to be established. This is still attempted, but as long as it established at least one healthy connection, it will delay the failure to connect to other members until they are attempted to be used. This can be important for pools like HikariCP which on failure may consider the connection unhealthy and needing to be replaced. See PR #21 for more details.
• MySQL dependency version updated to 8.0.15

0.8 Release

This release includes a range of internal improvements, feature expansions, and minor bug fixes.

Changes included in this release:

• mysql and psql transitive dependency version updates
• Minor performance improvements
• Added in ability to set more control over what delegate connection / server is used for a request: https://github.com/threadly/auroraArc/blob/e431b36bdb6be4c5440343bcf4214af614b5293b/arcCommon/src/main/java/org/threadly/db/aurora/DelegatingAuroraConnection.java#L31-L111
• Added in the ability to configure how often a server's master / slave status is polled: https://github.com/threadly/auroraArc/blob/c8049fdad3236bd24d6da21170232429fa25e81d/arcCommon/src/main/java/org/threadly/db/aurora/AuroraClusterMonitor.java#L47-L56
• DatabaseMetaData is now corrected to return information about the correct auroraArc connection

0.7 Postgresql Bug Fix Release

This release is only to address the issues with the psql driver released in 0.6 not working.