[ https://issues.apache.org/jira/browse/SOLR-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746403#comment-14746403 ]
Hoss Man commented on SOLR-8030: -------------------------------- bq. But aren't the docs in the tlog stored post update chain anyway? I'm pretty sure it's more complicated then that -- i suspect any processor that is configured to run _after_ the DistributedUpdateProcessor is at risk here in the event of tlog replay. > 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