[
https://issues.apache.org/jira/browse/CASSANDRA-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Eremeev updated CASSANDRA-6988:
-------------------------------------
Description:
When issuing execute_prepared_cql3_query through the thrift api with invalid
$queryId I get InvalidRequestException. I get same exception when attempting to
execute statement with invalid arguments. The only way to distinguish between
these errors is to parse error string in $why (which can be changed on server
side with version upgrade).
I think its would be nice to add $errorCode (similar to ones in binary
protocol, like 0x2500 for invalid query id) to InvalidRequestException in
thrift.
was:
When issuing execute_prepared_cql3_query through the thrift api with invalid
$queryId I get InvalidRequestException. I get same exception when attempting to
execute statement with invalid arguments. The only way to
distinguish between these errors is to parse error string in $why (which can be
changed on server side with version upgrade).
I think its would be nice to add $errorCode (similar to ones in binary
protocol, like 0x2500 for invalid query id) to InvalidRequestException in
thrift.
> Add error code to thrift InvalidRequestException
> ------------------------------------------------
>
> Key: CASSANDRA-6988
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6988
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Pavel Eremeev
>
> When issuing execute_prepared_cql3_query through the thrift api with invalid
> $queryId I get InvalidRequestException. I get same exception when attempting
> to execute statement with invalid arguments. The only way to distinguish
> between these errors is to parse error string in $why (which can be changed
> on server side with version upgrade).
> I think its would be nice to add $errorCode (similar to ones in binary
> protocol, like 0x2500 for invalid query id) to InvalidRequestException in
> thrift.
--
This message was sent by Atlassian JIRA
(v6.2#6252)