Class UnexpectedPagingException
- All Implemented Interfaces:
Serializable
This is not a core exception. It was added to the CQL activity type driver for nosqlbench specifically to catch the following unexpected condition: Paging would be needed to read all the results from a read query, but the user is not expecting to intentionally check and iterate the result sets for paging.
This should only be thrown if a result set would need paging, but configuration options specific that it should not expect to. Rather than assume paging is completely expected or unexpected, we simply assume that only 1 page is allowed, being the first page, or what is thought of as "not paging".
If this error is thrown, and paging is expected, then the user can adjust fetchsize or maxpages in order to open up paging to the degree that is allowable or expected.
- See Also:
-
Constructor Summary
ConstructorsConstructorDescriptionUnexpectedPagingException(com.datastax.oss.driver.api.core.cql.AsyncResultSet resultSet, String queryString, int fetchedPages, int maxpages, int fetchSize) -
Method Summary
Modifier and TypeMethodDescriptioncom.datastax.oss.driver.api.core.cql.AsyncResultSetMethods inherited from class java.lang.Throwable
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
-
Constructor Details
-
UnexpectedPagingException
public UnexpectedPagingException(com.datastax.oss.driver.api.core.cql.AsyncResultSet resultSet, String queryString, int fetchedPages, int maxpages, int fetchSize)
-
-
Method Details
-
getResultSet
public com.datastax.oss.driver.api.core.cql.AsyncResultSet getResultSet() -
getMessage
- Overrides:
getMessagein classThrowable
-