You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2016/08/28 20:08:20 UTC

[jira] [Created] (SOLR-9447) Do not clone SolrInputDocument if update processor chain does not contain custom processors

Shalin Shekhar Mangar created SOLR-9447:
-------------------------------------------

             Summary: Do not clone SolrInputDocument if update processor chain does not contain custom processors
                 Key: SOLR-9447
                 URL: https://issues.apache.org/jira/browse/SOLR-9447
             Project: Solr
          Issue Type: Improvement
      Security Level: Public (Default Security Level. Issues are Public)
          Components: SolrCloud
            Reporter: Shalin Shekhar Mangar
            Assignee: Shalin Shekhar Mangar
             Fix For: master (7.0), 6.3


In SOLR-3215 we started cloning documents before adding them locally and send the cloned copy to replicas. This was done because processors after DistributedUpdateProcessor can affect the docs before they are sent to the replicas.

However, we can avoid the deep copy if we know for sure that the processors after DUP are one of (LogUpdateProcessor, RunUpdateProcessor, TolerantUpdateProcessor) which definitely do not modify the document. This ensures that the common case is optimized.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org