lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Hatcher (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-8767) RealTimeGetComponent and stored/copyField exclusion
Date Tue, 01 Mar 2016 14:45:18 GMT

     [ https://issues.apache.org/jira/browse/SOLR-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Erik Hatcher updated SOLR-8767:
-------------------------------
    Description: 
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 in).

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?

  was:
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?


> 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 in).
> 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


Mime
View raw message