[
https://issues.apache.org/jira/browse/CASSANDRA-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408101#comment-16408101
]
Aleksey Yeschenko commented on CASSANDRA-14058:
-----------------------------------------------
Noticed a couple regressions when merging up CASSANDRA-14330:
1. {{DataResolver}} no longer uses
{{cassandra.drop_oversized_readrepair_mutations}} prop - and
{{DROP_OVERSIZED_READ_REPAIR_MUTATIONS}} constant is now unused, and the
feature is missing.
2. {{RowIteratorMergeListener}} re-thrown {{AssertionError}} no longer includes
the responses. This should be restored, as without it debugging RR issues is an
even worse, potentially impossible, nightmare.
Nit: In {{DataResolver}}, {{repairResults}} field is now unused.
> 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
> Priority: Major
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
