cql-io-0.14.5: Cassandra CQL client.

Safe HaskellNone
LanguageHaskell2010

Database.CQL.IO

Contents

Description

This driver operates on some state which must be initialised prior to executing client operations and terminated eventually. The library uses tinylog for its logging output and expects a Logger.

For example:

> import Data.Text (Text)
> import Data.Functor.Identity
> import Database.CQL.IO as Client
> import Database.CQL.Protocol
> import qualified System.Logger as Logger
>
> g <- Logger.new Logger.defSettings
> c <- Client.init g defSettings
> let p = QueryParams One False () Nothing Nothing Nothing
> runClient c $ query ("SELECT cql_version from system.local" :: QueryString R () (Identity Text)) p
[Identity "3.2.0"]
> shutdown c

Note on prepared statements

Prepared statements are fully supported but imply certain complexities which lead to some assumptions beyond the scope of the CQL binary protocol specification (spec):

  1. The spec scopes the QueryId to the node the query has been prepared with. The spec does not state anything about the format of the QueryId, however it seems that at least the official Java driver assumes that any given QueryString yields the same QueryId on every node. We make the same assumption.
  2. In case a node does not know a given QueryId an Unprepared error is returned. We assume that it is always safe to then transparently re-prepare the corresponding QueryString and to re-execute the original request against the same node.

Besides these assumptions there is also a potential tradeoff in regards to eager vs. lazy query preparation. We understand eager to mean preparation against all current nodes of a cluster and lazy to mean preparation against a single node if required, i.e. after an Unprepared error response. Which strategy to choose depends on the scope of query reuse and the size of the cluster. The global default can be changed through the Settings module and per action using withPrepareStrategy.

Synopsis

Client settings

data PrepareStrategy Source

Constructors

EagerPrepare

cluster-wide preparation

LazyPrepare

on-demand per node preparation

defSettings :: Settings Source

Default settings:

  • contact point is "localhost" port 9042
  • load-balancing policy is random
  • binary protocol version is 3 (supported by Cassandra >= 2.1.0)
  • connection idle timeout is 60s
  • the connection pool uses 4 stripes to mitigate thread contention
  • connections use a connect timeout of 5s, a send timeout of 3s and a receive timeout of 10s
  • 128 streams per connection are used
  • 16k receive buffer size
  • no compression is applied to frame bodies
  • no default keyspace is used.
  • no retries are done
  • lazy prepare strategy

addContact :: String -> Settings -> Settings Source

Add an additional host to the contact list.

setCompression :: Compression -> Settings -> Settings Source

Set the compression to use for frame body compression.

setConnectTimeout :: NominalDiffTime -> Settings -> Settings Source

Set the connect timeout of a connection.

setContacts :: String -> [String] -> Settings -> Settings Source

Set the initial contact points (hosts) from which node discovery will start.

setIdleTimeout :: NominalDiffTime -> Settings -> Settings Source

Set the connection idle timeout. Connections in a pool will be closed if not in use for longer than this timeout.

setKeyspace :: Keyspace -> Settings -> Settings Source

Set the default keyspace to use. Every new connection will be initialised to use this keyspace.

setMaxConnections :: Int -> Settings -> Settings Source

Maximum connections per pool stripe.

setMaxStreams :: Int -> Settings -> Settings Source

Set the maximum number of streams per connection. In version 2 of the binary protocol at most 128 streams can be used. Version 3 supports up to 32768 streams.

setMaxTimeouts :: Int -> Settings -> Settings Source

When receiving a response times out, we can no longer use the stream of the connection that was used to make the request as it is uncertain if a response will arrive later. Thus the bandwith of a connection will be decreased. This settings defines a threshold after which we close the connection to get a new one with all streams available.

setPolicy :: IO Policy -> Settings -> Settings Source

Set the load-balancing policy.

setPoolStripes :: Int -> Settings -> Settings Source

Set the number of pool stripes to use. A good setting is equal to the number of CPU cores this codes is running on.

setPortNumber :: PortNumber -> Settings -> Settings Source

Set the portnumber to use to connect on every node of the cluster.

setPrepareStrategy :: PrepareStrategy -> Settings -> Settings Source

Set strategy to use for preparing statements.

setProtocolVersion :: Version -> Settings -> Settings Source

Set the binary protocol version to use.

setResponseTimeout :: NominalDiffTime -> Settings -> Settings Source

Set the receive timeout of a connection. Requests exceeding the receive timeout will fail with a Timeout exception.

setSendTimeout :: NominalDiffTime -> Settings -> Settings Source

Set the send timeout of a connection. Request exceeding the send will cause the connection to be closed and fail with ConnectionClosed exception.

setRetrySettings :: RetrySettings -> Settings -> Settings Source

Set default retry settings to use.

setMaxRecvBuffer :: Int -> Settings -> Settings Source

Set maximum receive buffer size.

The actual buffer size used will be the minimum of the CQL response size and the value set here.

Retry Settings

retryForever :: RetrySettings Source

Forever retry immediately.

maxRetries :: Word -> RetrySettings -> RetrySettings Source

Limit number of retries.

adjustConsistency :: Consistency -> RetrySettings -> RetrySettings Source

When retrying a (batch-) query, change consistency to the given value.

constDelay :: NominalDiffTime -> RetrySettings -> RetrySettings Source

Wait a constant time between retries.

expBackoff Source

Arguments

:: NominalDiffTime

Initial delay.

-> NominalDiffTime

Maximum delay.

-> RetrySettings 
-> RetrySettings 

Delay retries with exponential backoff.

fibBackoff Source

Arguments

:: NominalDiffTime

Initial delay.

-> NominalDiffTime

Maximum delay.

-> RetrySettings 
-> RetrySettings 

Delay retries using Fibonacci sequence as backoff.

adjustSendTimeout :: NominalDiffTime -> RetrySettings -> RetrySettings Source

On retry adjust the send timeout.

adjustResponseTimeout :: NominalDiffTime -> RetrySettings -> RetrySettings Source

On retry adjust the response timeout.

Query Runner

class RunQ q where Source

A type which can run a query against Cassandra.

Methods

runQ :: (MonadClient m, Tuple a, Tuple b) => q k a b -> QueryParams a -> m (Response k a b) Source

Client monad

data Client a Source

The Client monad.

A simple reader monad around some internal state. Prior to executing this monad via runClient, its state must be initialised through init and after finishing operation it should be terminated with shutdown.

Actual CQL queries are handled by invoking request. Additionally debugInfo returns an internal cluster view.

class (Functor m, Applicative m, Monad m, MonadIO m, MonadCatch m) => MonadClient m where Source

Monads in which Client actions may be embedded.

Methods

liftClient :: Client a -> m a Source

Lift a computation to the Client monad.

localState :: (ClientState -> ClientState) -> m a -> m a Source

Execute an action with a modified ClientState.

data ClientState Source

Opaque client state/environment.

data DebugInfo Source

Constructors

DebugInfo 

Fields

policyInfo :: String

Policy string representation

jobInfo :: [InetAddr]

hosts currently checked for reachability

hostInfo :: [Host]

all known hosts

Instances

init :: MonadIO m => Logger -> Settings -> m ClientState Source

Initialise client state with the given Settings using the provided Logger for all it's logging output.

runClient :: MonadIO m => ClientState -> Client a -> m a Source

Execute the client monad.

retry :: MonadClient m => RetrySettings -> m a -> m a Source

Use given RetrySettings during execution of some client action.

shutdown :: MonadIO m => ClientState -> m () Source

Terminate client state, i.e. end all running background checks and shutdown all connection pools. Once this is entered, the client will eventually be shut down, though an asynchronous exception can interrupt the wait for that to occur.

query :: (MonadClient m, Tuple a, Tuple b, RunQ q) => q R a b -> QueryParams a -> m [b] Source

Run a CQL read-only query against a Cassandra node.

query1 :: (MonadClient m, Tuple a, Tuple b, RunQ q) => q R a b -> QueryParams a -> m (Maybe b) Source

Run a CQL read-only query against a Cassandra node.

write :: (MonadClient m, Tuple a, RunQ q) => q W a () -> QueryParams a -> m () Source

Run a CQL insert/update query against a Cassandra node.

schema :: (MonadClient m, Tuple a, RunQ q) => q S a () -> QueryParams a -> m (Maybe SchemaChange) Source

Run a CQL schema query against a Cassandra node.

trans :: (MonadClient m, Tuple a, RunQ q) => q W a Row -> QueryParams a -> m [Row] Source

Run a CQL insert/update query as a "lightweight transaction" against a Cassandra node.

data Page a Source

Return value of paginate. Contains the actual result values as well as an indication of whether there is more data available and the actual action to fetch the next page.

Constructors

Page 

Fields

hasMore :: !Bool
 
result :: [a]
 
nextPage :: Client (Page a)
 

Instances

emptyPage :: Page a Source

A page with an empty result list.

paginate :: (MonadClient m, Tuple a, Tuple b, RunQ q) => q R a b -> QueryParams a -> m (Page b) Source

Run a CQL read-only query against a Cassandra node.

This function is like query, but limits the result size to 10000 (default) unless there is an explicit size restriction given in QueryParams. The returned Page can be used to continue the query.

Please note that -- as of Cassandra 2.1.0 -- if your requested page size is equal to the result size, hasMore might be true and a subsequent nextPage will return an empty list in result.

Prepared Queries

data PrepQuery k a b Source

Representation of a prepared query. Actual preparation is handled transparently by the driver.

Instances

Batch

data BatchM a Source

Batch construction monad.

addQuery :: (Show a, Tuple a, Tuple b) => QueryString W a b -> a -> BatchM () Source

Add a query to this batch.

addPrepQuery :: (Show a, Tuple a, Tuple b) => PrepQuery W a b -> a -> BatchM () Source

Add a prepared query to this batch.

setType :: BatchType -> BatchM () Source

Set the type of this batch.

setConsistency :: Consistency -> BatchM () Source

Set Batch consistency level.

setSerialConsistency :: SerialConsistency -> BatchM () Source

Set Batch serial consistency.

batch :: MonadClient m => BatchM () -> m () Source

Run a batch query against a Cassandra node.

low-level

request :: (MonadClient m, Tuple a, Tuple b) => Request k a b -> m (Response k a b) Source

Send a CQL Request to the server and return a Response.

This function will first ask the clients load-balancing Policy for some host and use its connection pool to acquire a connection for request transmission.

If all available hosts are busy (i.e. their connection pools are fully utilised), the function will block until a connection becomes available or the maximum wait-queue length has been reached.

Policies

data Policy Source

A policy defines a load-balancing strategy and generally handles host visibility.

Constructors

Policy 

Fields

setup :: [Host] -> [Host] -> IO ()

Initialise the policy with two sets of hosts. The first parameter are hosts known to be available, the second are other nodes. Please note that a policy may be re-initialised at any point through this method.

onEvent :: HostEvent -> IO ()

Event handler. Policies will be informed about cluster changes through this function.

select :: IO (Maybe Host)

Host selection. The driver will ask for a host to use in a query through this function. A policy which has no available nodes my return Nothing.

current :: IO [Host]

Return all currently alive hosts.

acceptable :: Host -> IO Bool

During startup and node discovery, the driver will ask the policy if a dicovered host should be ignored.

hostCount :: IO Word

During query processing, the driver will ask the policy for a rough esitimate of alive hosts. The number is used to repeatedly invoke select (with the underlying assumption that the policy returns mostly different hosts).

display :: IO String

Like having an effectful Show instance for this policy.

random :: IO Policy Source

Return hosts in random order.

roundRobin :: IO Policy Source

Iterate over hosts one by one.

Hosts

data Host Source

Host representation.

data HostEvent Source

This event will be passed to a Policy to inform it about cluster changes.

Constructors

HostNew !Host

a new host has been added to the cluster

HostGone !InetAddr

a host has been removed from the cluster

HostUp !InetAddr

a host has been started

HostDown !InetAddr

a host has been stopped

hostAddr :: Lens' Host InetAddr Source

The IP address and port number of this host.

dataCentre :: Lens' Host Text Source

The data centre name (may be an empty string).

rack :: Lens' Host Text Source

The rack name (may be an empty string).

Exceptions