[jira] [Created] (SOLR-14838) Atomic updates when the destination for a copyField has stored=true

["Erick Erickson (Jira)" <ji...@apache.org>]

Erick Erickson created SOLR-14838:
-------------------------------------

             Summary: Atomic updates when the destination for a copyField has stored=true
                 Key: SOLR-14838
                 URL: https://issues.apache.org/jira/browse/SOLR-14838
             Project: Solr
          Issue Type: Improvement
      Security Level: Public (Default Security Level. Issues are Public)
            Reporter: Erick Erickson


Raising for discussion. Currently, when using atomic updates, one restriction is that the destination for copyField directives must have stored=false or you wind up with duplicate entries.

On the surface and just glancing at AtomicUpdateDocumentMerger, it seems like we could just skip adding fields to the "toDoc" if they were the destinations of a copyField directive.

Or does this run afoul of things like Real Time Get?

[~yonik] do you recall anything about this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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