[SOLR-8767] RealTimeGetComponent and stored/copyField exclusion

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Component/s: SolrCloud
• Assignee: Unassigned
• Reporter: Erik Hatcher
• Created: 01/Mar/16 14:44
• Updated: 03/May/18 00:59

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?

Issue Links

• is broken by: SOLR-3743 stored copyField targets, optimistic concurrency, atomic updates