The supported error codes are described below:
0x0000 Server error: something unexpected happened. This indicates a
server-side bug.
0x000A Protocol error: some client message triggered a protocol
violation (for instance a QUERY message is sent before a STARTUP
one has been sent)
0x0100 Bad credentials: CREDENTIALS request failed because Cassandra
did not accept the provided credentials.
0x1000 Unavailable exception. The rest of the ERROR message body will be
<cl><required><alive>
where:
<cl> is the consistency level of the query having triggered
the exception.
<required> is an int representing the number of node that
should be alive to respect <cl>
<alive> is an int representing the number of replica that
were known to be alive when the request has been
processed (since an unavailable exception has been
triggered, there will be <alive> < <required>)
0x1001 Overloaded: the request cannot be processed because the
coordinator node is overloaded
0x1002 Is_bootstrapping: the request was a read request but the
coordinator node is bootstrapping
0x1003 Truncate_error: error during a truncation error.
0x1100 Write_timeout: Timeout exception during a write request. The rest
of the ERROR message body will be
<cl><received><blockfor><writeType>
where:
<cl> is the consistency level of the query having triggered
the exception.
<received> is an int representing the number of nodes having
acknowledged the request.
<blockfor> is the number of replica whose acknowledgement is
required to achieve <cl>.
<writeType> is a string that describe the type of the write
that timeouted. The value of that string can be one
of:
- "SIMPLE": the write was a non-batched
non-counter write.
- "BATCH": the write was a (logged) batch write.
If this type is received, it means the batch log
has been successfully written (otherwise a
"BATCH_LOG" type would have been send instead).
- "UNLOGGED_BATCH": the write was an unlogged
batch. Not batch log write has been attempted.
- "COUNTER": the write was a counter write
(batched or not).
- "BATCH_LOG": the timeout occured during the
write to the batch log when a (logged) batch
write was requested.
*7. Error codes
The supported error codes are described below: 0x0000 Server error: something unexpected happened. This indicates a server-side bug. 0x000A Protocol error: some client message triggered a protocol violation (for instance a QUERY message is sent before a STARTUP one has been sent) 0x0100 Bad credentials: CREDENTIALS request failed because Cassandra did not accept the provided credentials.
0x1000 Unavailable exception. The rest of the ERROR message body will be <cl><required><alive> where: <cl> is the consistency level of the query having triggered the exception. <required> is an int representing the number of node that should be alive to respect <cl> <alive> is an int representing the number of replica that were known to be alive when the request has been processed (since an unavailable exception has been triggered, there will be <alive> < <required>) 0x1001 Overloaded: the request cannot be processed because the coordinator node is overloaded 0x1002 Is_bootstrapping: the request was a read request but the coordinator node is bootstrapping 0x1003 Truncate_error: error during a truncation error. 0x1100 Write_timeout: Timeout exception during a write request. The rest of the ERROR message body will be <cl><received><blockfor><writeType> where: <cl> is the consistency level of the query having triggered the exception. <received> is an int representing the number of nodes having acknowledged the request. <blockfor> is the number of replica whose acknowledgement is required to achieve <cl>. <writeType> is a string that describe the type of the write that timeouted. The value of that string can be one of: - "SIMPLE": the write was a non-batched non-counter write. - "BATCH": the write was a (logged) batch write. If this type is received, it means the batch log has been successfully written (otherwise a "BATCH_LOG" type would have been send instead). - "UNLOGGED_BATCH": the write was an unlogged batch. Not batch log write has been attempted. - "COUNTER": the write was a counter write (batched or not). - "BATCH_LOG": the timeout occured during the write to the batch log when a (logged) batch write was requested.