You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Erik Hatcher (JIRA)" <ji...@apache.org> on 2016/03/01 15:45:18 UTC

[jira] [Created] (SOLR-8767) RealTimeGetComponent and stored/copyField exclusion

Erik Hatcher created SOLR-8767:
----------------------------------

             Summary: RealTimeGetComponent and stored/copyField exclusion
                 Key: SOLR-8767
                 URL: https://issues.apache.org/jira/browse/SOLR-8767
             Project: Solr
          Issue Type: Bug
          Components: SolrCloud
            Reporter: Erik Hatcher
            Priority: Critical


Consider this scenario: schema has fields `a` and `b` defined, both stored.  A copyField is defined from `a` => `b`.  A document is indexed with `id=1; b="foo"`.  A real-time /get will not return field `b` because RealTimeGetComponent.toSolrDoc currently excludes copyField destinations (despite, in this situation, the source of that copyField not being sent it).

Granted this is a bit of a diabolical case (discovered while tinkering with cloud MLT tests), but isn't that far fetched to happen in the wild.

Maybe real-time /get should return all fields set as stored, regardless of copyField status?



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