[
https://issues.apache.org/jira/browse/CASSANDRA-14353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-14353:
----------------------------------------
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
bq. A part of me thinks that the extra two catch-rethrows in DataResolver are
unnecessary
I don't disagree... but there are asserts in that path and I'm already wrapping
the iterator. I'd feel kinda dumb if I ended having a debug some rare instance
where they could have helped.
Committed as {{eda2613bcca7e4734b3bb4e04c6a4df39eb59ca2}}
> Fix some regressions caused by 14058
> ------------------------------------
>
> Key: CASSANDRA-14353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14353
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Blake Eggleston
> Assignee: Blake Eggleston
> Priority: Major
> Fix For: 4.0
>
>
> As [~iamaleksey] pointed out, CASSANDRA-14058 introduced a few regressions:
> {quote}
> 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.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
