[ 
https://issues.apache.org/jira/browse/SOLR-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365544#comment-14365544
 ] 

Hoss Man commented on SOLR-7257:
--------------------------------

bq. In realtimegetcomponent i noticed a "if isCopyFieldTarget(..)" that prevent 
the field to be returned but i couldn't find similar filter in search results.

pretty sure this was added as a hack to ensure RTG would have consistent 
behavior regardless of wether the doc was returned from the index, or from the 
updateLog (which is before schema copyFields are evaluated)

There's a specific comment about this on the ref guide page for RTG, but no one 
familiar with the details of the code has bothered to try and help address this 
on the documentation side...

https://cwiki.apache.org/confluence/display/solr/RealTime+Get

an alternative that may work well in some cases is to remove copyFields from 
your schema.xml and instead use the CloneFieldUpdateProcessorFactory to ensure 
the Document has all of it's fields before the distributed processor (which 
maintains the updateLog on the leader) gets the document.

> copyfieldtargets are not returned
> ---------------------------------
>
>                 Key: SOLR-7257
>                 URL: https://issues.apache.org/jira/browse/SOLR-7257
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.10.3
>            Reporter: Paolo Cappuccini
>
> copyfieldtargets are purged from field list in realtimeget and search results 
> even if they are declared in schema like stored fields.
> If i understood the source code if declared like stored fields they are 
> correctly saved in lucene index but there is not way to return them.
> This is a bug or intended behaviour?
> Perhaps it should be checked if the copied field is stored and return value 
> in searches and gets.
> Thanks



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to