[
https://issues.apache.org/jira/browse/CASSANDRA-16175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17407713#comment-17407713
]
Ekaterina Dimitrova commented on CASSANDRA-16175:
-------------------------------------------------
The issue was initially raised to be fixed for 4.x and I ported below a patch
from [~jasonstack], CI started
||Patch||CI||
|
[trunk|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:16175-trunk?expand=1]
| [Jenkins dev run |
https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1089/] |
I personally think we can port the patch also to 3.0, 3.11 and 4.0 so I did it.
CI can be run for all branches pre-commit when we confirm the versions which
will be fixed.
||Patch||
|[3.0|https://github.com/ekaterinadimitrova2/cassandra/pull/new/16175-3.0]|
|[3.11|https://github.com/ekaterinadimitrova2/cassandra/pull/new/16175-3.11]|
|[4.0|https://github.com/ekaterinadimitrova2/cassandra/pull/new/16175-4.0]|
> Avoid removing batch when it's not created during view replication
> ------------------------------------------------------------------
>
> Key: CASSANDRA-16175
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16175
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
> Reporter: Zhao Yang
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.x
>
>
> When the base replica is also a view replica we don't write a local batchlog,
> but they are unnecessarily removed when the view write is successful, what
> creates (and persists) a tombstone into the system.batches table.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
