You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2020/03/30 20:13:00 UTC

[jira] [Created] (SOLR-14375) AtomicUpdateDocumentMerger should allow fields not in the schema

David Smiley created SOLR-14375:
-----------------------------------

             Summary: AtomicUpdateDocumentMerger should allow fields not in the schema
                 Key: SOLR-14375
                 URL: https://issues.apache.org/jira/browse/SOLR-14375
             Project: Solr
          Issue Type: Improvement
      Security Level: Public (Default Security Level. Issues are Public)
            Reporter: David Smiley


AtomicUpdateDocumentMerger processes SolrInputDocuments that are partial that have partial/atomic update commands embedded within them.  Using add or set on a field that isn't in the schema will currently result in an error that the field does not exist.  I think this is a small bug since it's okay to work with fields not in the schema in the URP chain as there may be follow-on URPs that subsequently consume them.

See getNativeFieldValue which should be enhanced to call schema.getFieldOrNull



--
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