[
https://issues.apache.org/jira/browse/SOLR-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212255#comment-15212255
]
David Smiley commented on SOLR-8030:
------------------------------------
After resolving this issue in a big search app last week, I actually did need
to configure the URP chain for the UpdateLog separate from the "normal"
document URP. The details why aren't that important, and if I had absolutely
no way of customizing the chain for the UpdateLog replay, I could have found
other means to achieve my aims, at least for this app. So I think there's no
change in Solr needed here aside from clearer docs. Alternatively, to make
this less of a gotcha, Solr could perhaps look up a chain by a special name,
such as \_updateLogReplay\_ which would be defaulted to be Distributed URP +
RunURP if not found.
> 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
> Attachments: SOLR-8030.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
