Hoogle Search

Within LTS Haskell 24.64 (ghc-9.10.3)

Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.

Exact lookup

1. UA_RetryOnConflict :: Int -> UpsertActionMetadata

   bloodhound	Database.Bloodhound.Common.Types

   No documentation available.

2. defRetryHandlers :: forall (m :: Type -> Type) . Monad m => [RetryStatus -> Handler m Bool]

   cql-io	Database.CQL.IO

   The default retry handlers permit a retry for the following errors:

   • A HostError, since it always occurs before a query has been sent to the server.
   • A ConnectionError that is a ConnectTimeout, since it always occurs before a query has been sent to the server.
   • A ResponseError that is one of the following:
     • Unavailable, since that is an error response from a coordinator before the query is actually executed.
     • A ReadTimeout that indicates that the required consistency level could be achieved but the data was unfortunately chosen by the coordinator to be returned from a replica that turned out to be unavailable. A retry has a good chance of getting the data from one of the other replicas.
     • A WriteTimeout for a write to the batch log failed. The batch log is written prior to execution of the statements of the batch and hence these errors are safe to retry.

3. defRetryPolicy :: RetryPolicy

   cql-io	Database.CQL.IO

   The default retry policy permits a single, immediate retry.

4. defRetrySettings :: RetrySettings

   cql-io	Database.CQL.IO

   Default retry settings, combining defRetryHandlers with defRetryPolicy. Consistency is never reduced on retries and timeout values remain unchanged.

5. eagerRetryHandlers :: forall (m :: Type -> Type) . Monad m => [RetryStatus -> Handler m Bool]

   cql-io	Database.CQL.IO

   The eager retry handlers permit a superset of the errors of defRetryHandlers, namely:

   • Any ResponseError that is a ReadTimeout, WriteTimeout, Overloaded, Unavailable or ServerError.
   • Any ConnectionError.
   • Any IOException.
   • Any HostError.
   • Any SomeSSLException (if an SSL context is configured).
   Notably, these retry handlers are only safe to use for idempotent queries, or if a duplicate write has no severe consequences in the context of the application's data model.

6. eagerRetryPolicy :: RetryPolicy

   cql-io	Database.CQL.IO

   The eager retry policy permits 5 retries with exponential backoff (base-2) with an initial delay of 100ms, i.e. the retries will be performed with 100ms, 200ms, 400ms, 800ms and 1.6s delay, respectively, for a maximum delay of ~3s.

7. eagerRetrySettings :: RetrySettings

   cql-io	Database.CQL.IO

   Eager retry settings, combining eagerRetryHandlers with eagerRetryPolicy. Consistency is never reduced on retries and timeout values remain unchanged.

8. noRetry :: RetrySettings

   cql-io	Database.CQL.IO

   Never retry.

9. setRetryHandlers :: (forall (m :: Type -> Type) . Monad m => [RetryStatus -> Handler m Bool]) -> RetrySettings -> RetrySettings

   cql-io	Database.CQL.IO

   Set the exception handlers that decide whether a request can be retried by the client, i.e. what errors are permissible to retry. For configuring how the retries are performed, see setRetryPolicy.

10. setRetryPolicy :: RetryPolicy -> RetrySettings -> RetrySettings

    cql-io	Database.CQL.IO

    Set the RetryPolicy to apply on retryable exceptions, which determines the number and distribution of retries over time, i.e. how retries are performed. Configuring a retry policy does not specify what errors should actually be retried. See setRetryHandlers.

Page 22 of many | Previous | Next