lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] [Commented] (SOLR-2822) don't run update processors twice
Date Fri, 25 May 2012 13:04:24 GMT


Mark Miller commented on SOLR-2822:

+1 - approach seems as elegant as we could shoot for right now. I much prefer it to juggling
multiple chains.

I still worry about the 'clone doc' issue and update procs between distrib and run - if we
do decide to not let procs live there, we should probably hard fail on it.

Latest patch looks good to me - let's commit and iterate on trunk.
> don't run update processors twice
> ---------------------------------
>                 Key: SOLR-2822
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud, update
>            Reporter: Yonik Seeley
>             Fix For: 4.0
>         Attachments: SOLR-2822.patch, SOLR-2822.patch, SOLR-2822.patch
> An update will first go through processors until it gets to the point where it is forwarded
to the leader (or forwarded to replicas if already on the leader).
> We need a way to skip over the processors that were already run (perhaps by using a processor
chain dedicated to sub-updates?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message