[SOLR-2822] don't run update processors twice

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0-ALPHA
• Component/s: SolrCloud, update
• Assignee: Chris M. Hostetter
• Reporter: Yonik Seeley
• Created: 11/Oct/11 14:19
• Updated: 10/May/13 10:39
• Resolved: 25/May/12 17:26

Description

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?

Issue Links

• is related to: SOLR-3257 Dedupe update.chain example should include DistribtedUpdateProcessorFactory
• relates to: SOLR-3473 Distributed deduplication broken when using non-uniqueKey for signatureField
• relates to: SOLR-3215 We should clone the SolrInputDocument before adding locally and then send that clone to replicas.