- Support for CLI-based migration
Cluster
andSession
instances can now be injected (thanks to domax for PR 23)AddressTranslator
is now configurable (thanks to MALPI for PR 26)
- Upgraded to Dropwizard
1.0.0
. This includes an upgrade to Java 8, hence the major version bump.
- Upgraded to use version
3.1.0
of the Cassandra Driver
- Updated
validationQuery
to work across a broader range of Cassandra versions (thanks to adejanovski for PR 20)
- Simplified the versioning scheme to use Semantic Versioning, largely based on Issue 19
- Upgraded to use version
3.0.0
of the Cassandra Driver at the request of devshorts in Issue 17 - Migrated
dropwizard-cassandra
from GitHub user stuartgunter to GitHub organisation composable-systems - Changed Maven groupId from
org.stuartgunter
tosystems.composable
- Changed root package from
org.stuartgunter
tosystems.composable
- Changed default healthcheck query to support newer versions of Cassandra
- First class support for SSL configuration using either
jdk
ornetty
(andnetty
supports eitherjdk
oropenssl
providers)
- Modified
contactPoints
to use all A records associated with DNS names instead of just one A record per DNS name (thanks to manub for PR 14). This should not be a breaking change, but the version bump to2.0
is precautionary as it informs users to be aware of the change in behaviour.
- Added support for
LoadBalancingPolicy
via YAML configuration (credit to adejanovski for PR 12 that sparked this) - Added support for
SpeculativeExecutionPolicy
via YAML configuration
- Upgraded to Dropwizard 0.8.1
- Upgraded to DataStax Cassandra Driver 2.1.2 (note: this includes breaking changes in the definition of
ProtocolVersion
- only relevant if you explicitly configure it though)
- Issue 8 Changed versioning scheme to incorporate Dropwizard version.
- Removed the deprecated
CassandraBundle
(superceded byCassandraFactory
in v0.4) - Upgraded to DataStax Cassandra Driver 2.0.6
- Upgraded to Dropwizard 0.7.1
- Pull 7 Upgraded to 2.0.3 Datastax Cassandra Driver
- Pull 6 Add
build()
overload that doesn't useEnvironment
CassandraHealthCheck
now uses a validation query instead of relying on the driver, which was giving false positives
- Issue 5 Changed implementation of
CassandraHealthCheck
to work around driver memory leak - Removed
SessionFactory
, as this was not adding any real value and might encourage poor use ofSession
instances - Pull 3 Use
InetAddress
for contactPoints - Pull 2 Fix null clusterName in log messages
- Pull 1 Make building independent of the Bundle
- Added
SessionFactory
to allow for easy session initialisation based on configuration (a session is established with the configuredkeyspace
, or directly to the cluster if a keyspace is not configured)
- Changed scope of dependencies from
provided
tocompile
- Fixed issues relating to generation of JavaDoc
- Added logging to
CassandraHealthCheck
- Updated license information and notices
- Updated docs on configuration
- Improved JavaDoc
- Provided
CassandraBundle
to build the cluster and register the relevant components - Provided
CassandraHealthCheck
to establish whether a session can be initialised as per configuration - Provided
CassandraManager
to ensure the cluster is appropriately closed on application shutdown - Provided
CassandraMetricSet
to expose metrics named according to the cluster - Provided
CassandraFactory
and related configuration classes to allow for full configuration of the Cassandra cluster