[
https://issues.apache.org/jira/browse/CASSANDRA-12774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15584338#comment-15584338
]
Kurt Greaves commented on CASSANDRA-12774:
------------------------------------------
It looks like at least EACH_QUORUM does pass through the DC to UE?
https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/db/ConsistencyLevel.java#L324
It doesn't for LOCAL_QUORUM however, which may be an issue I suppose.
> Expose dc in Unavailable exception errors
> -----------------------------------------
>
> Key: CASSANDRA-12774
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12774
> Project: Cassandra
> Issue Type: Bug
> Reporter: Andy Tolbert
> Priority: Minor
>
> For protocol v5 or later, it could be useful if Unavailable optionally
> included the DC that could not meet the CL.
> For example. if a user has a keyspace with RF of { dc1: 3, dc2: 3 } and they
> make a query at {{EACH_QUORUM}} and not enough replicas are available in dc2,
> an {{UnavailableException}} will be sent to the client with X available and 2
> required, but we don't know which DC failed. It looks like
> {{UnavailableException}} already has a constructor that takes in the DC (see
> [here|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/exceptions/UnavailableException.java#L33])
> so this could be feasible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
