connectors
Represents a single Cassandra keySpace.
Represents a single Cassandra keySpace.
Provides access to the associated Session as well as to a
Connector trait that can be mixed into CassandraTable
instances.
The default SessionProvider implementation, which should be sufficient for the most use cases.
The default SessionProvider implementation, which should be sufficient for the most use cases.
This implementation caches Session instances per keySpace.
A builder for KeySpace instances.
A builder for KeySpace instances.
When using multiple keySpaces in the same Cassandra cluster,
it is recommended to create all KeySpace instances from the
same builder instance.
This exists to prevent a dependency on the diesel engine or any kind of specific query implementation from within the connectors framework.
This exists to prevent a dependency on the diesel engine or any kind of specific query implementation from within the connectors framework. This allows connectors to be used in isolation from the rest of phantom DSL.
Responsible for providing Session instances of the Cassandra driver for multiple keySpaces defined in the same cluster.
(Since version 2.0.0) Renamed to the more descriptive CassandraConnection
Entry point for defining a keySpace based on a single contact point (Cassandra node).
Entry point for defining a keySpace based on a single contact point (Cassandra node).
Using a single contact point only is usually only recommended for testing purposes.
Entry point for defining a keySpace based on multiple contact points (Cassandra nodes).
Entry point for defining a keySpace based on multiple contact points (Cassandra nodes).
Even though the Cassandra driver technically only needs a single contact point and will then fetch the metadata for all other Cassandra nodes, it is recommended to specify more than just one contact point in case one node is down the moment the driver initializes.
Since the driver finds additional nodes on its own, the initial list of contact points only needs to be updated when you remove one of the specified contact points, not when merely adding new nodes to the cluster.