[
https://issues.apache.org/jira/browse/CASSANDRA-13226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938562#comment-15938562
]
Blake Eggleston commented on CASSANDRA-13226:
---------------------------------------------
[~brstgt] I think the idea behind flushing on stream for full is that you'll be
streaming even more recent data than when the merkle tree was generated, which
there's really no harm in doing.
> StreamPlan for incremental repairs flushing memtables unnecessarily
> -------------------------------------------------------------------
>
> Key: CASSANDRA-13226
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13226
> Project: Cassandra
> Issue Type: Bug
> Reporter: Blake Eggleston
> Assignee: Blake Eggleston
> Priority: Minor
> Fix For: 4.0
>
>
> Since incremental repairs are run against a fixed dataset, there's no need to
> flush memtables when streaming for them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
