You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Blake Eggleston (JIRA)" <ji...@apache.org> on 2017/11/17 22:37:00 UTC
[jira] [Commented] (CASSANDRA-14058) Refactor read executor and
response resolver, abstract read repair
[ https://issues.apache.org/jira/browse/CASSANDRA-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257694#comment-16257694 ]
Blake Eggleston commented on CASSANDRA-14058:
---------------------------------------------
I have an initial approach here https://github.com/bdeggleston/cassandra/tree/14058 that:
* adds a {{ReadRepair}} interface, and 2 implementations: noop and blocking
* Move read repair and short read implementation details out of DataResolver
* Added a {{service.reads}} package <- any thoughts on moving the other read related classes from {{service}} in there?
* removes DigestMismatchException
> Refactor read executor and response resolver, abstract read repair
> ------------------------------------------------------------------
>
> Key: CASSANDRA-14058
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14058
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Blake Eggleston
> Assignee: Blake Eggleston
> Fix For: 4.0
>
>
> CASSANDRA-10726 is stuck right now because the state of {{AbstractReadExecutor}} and {{DataResolver}} make it difficult to cleanly implement. It also looks like some additional read repair strategies might be added. This goal of this ticket is to clean up the structure of some of the read path components to make CASSANDRA-10726 doable, and additional read repair strategies possible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org