Skip to content

Releases: threadly/auroraArc

0.6 Release

22 May 02:27
Compare
Choose a tag to compare

Provides psql support, moving the artifact coordinates from org.threadly:auroraArc to either org.threadly:auroraArc-mysql or org.threadly:aurora-psql.

0.5 Release

15 Jan 22:15
Compare
Choose a tag to compare

Changes / improvements included in this release:

  • Added JNDI DataSource implementations
  • Upgraded threadly dependency
  • Fixed unlikely issue where an IndexOutOfBoundsException may occur from the AuroraClusterMonitor due to Math.abs(Integer.MIN_VALUE) overflow issue

0.4 Release with threadly upgrade

28 Dec 15:10
Compare
Choose a tag to compare

Primarily upgraded threadly to 5.8 and used new CentralThreadlyPool for the cluster monitor to reduce application thread sprawl.

0.3 Bug fix release

06 Nov 16:11
Compare
Choose a tag to compare

Includes several minor improvements in code and testing. However most notable fixes are:

  • Fixed thread safety in prepared statements, particularly when canceling
  • isClosed() status is verified against all delegate connections in case an exception or other behavior caused one to close without us being aware.

Bug fix release 0.2

24 Aug 00:02
Compare
Choose a tag to compare

Fix issue where Statements may never close

Because close() does not return a result, we would queue the close. Since close is often times the last action, this meant that we may never invoke close().
This was specifically shown to have problems after trying to reuse a connection that was providing a streaming result.

Initial 0.1 release!

23 Jul 23:11
Compare
Choose a tag to compare

This is the first release of the AuroraArc driver. There is still many more features and improvements to come. However this is a starting point, and should be usable in the right situations. This should have some level of stability, particularly when used with HikariCP and JDBI since those libraries have had the most testing.

If you have any questions, suggestions, or find defects, please file issues on GitHub and they will be addressed!