[
https://issues.apache.org/jira/browse/CASSANDRA-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347976#comment-15347976
]
Sylvain Lebresne commented on CASSANDRA-12075:
----------------------------------------------
I think the idea is to indicate whether the query was idempotent in the first
place or not. So a timeout on a counter update, or a list append would say it
isn't.
And I don't think that's crazy since currently client have to often rely on
client declaring whether the query is idempotent since they don't parse queries
(and kind of need to know on timeout for the purpose of retrying).
That said, I think it's mostly useful for timeout exception, not all
{{RequestExecutionException}} as I believe the other exceptions are precise
enough for client to make their decision). I also don't think there is cases
where we can meaningfully say it should be retried on a different host.
But anyway, insofar as this ticket is about adding a boolean {{isIdemptotent}}
to timeout exceptions, then I'm in favor of that. This is protocol v5 thing
though.
> Include whether or not the client should retry the request when throwing a
> RequestExecutionException
> ----------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-12075
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12075
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Geoffrey Yu
> Assignee: Geoffrey Yu
> Priority: Minor
>
> Some requests that result in an error should not be retried by the client.
> Right now if the client gets an error, it has no way of knowing whether or
> not it should retry. We can include an extra field in each
> {{RequestExecutionException}} that will indicate whether the client should
> retry, retry on a different host, or not retry at all.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
