[
https://issues.apache.org/jira/browse/SOLR-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738859#comment-14738859
]
ludovic Boutros commented on SOLR-8030:
---------------------------------------
[~ichattopadhyaya],
you could create an update processor which forbid deleteByQuery updates.
Then put it in the default update chain.
You can create another update chain without this processor.
Add some documents and delete them with queries with the update chain allowing
this operation.
Next, play with the famous Monkey ;)
Perhaps, are there easier ways to reproduce ?
I can try do reproduce this, I like the Monkey :p.
> Transaction log does not store the update chain used for updates
> ----------------------------------------------------------------
>
> Key: SOLR-8030
> URL: https://issues.apache.org/jira/browse/SOLR-8030
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 5.3
> Reporter: ludovic Boutros
>
> Transaction Log does not store the update chain used during updates.
> Therefore tLog uses the default update chain during log replay.
> If we implement custom update logic with multiple update chains, the log
> replay could break this logic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
