I think the suggestion I have seen is that copyField should be index-only and - therefore - will not be returned. It is primarily there to make searching easier by aggregating fields or to provide alternative analyzer pipeline.
Can you make your copyField destination not stored? Regards, Alex. Personal blog: http://blog.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Wed, Jun 5, 2013 at 10:37 AM, Robert Krüger <krue...@lesspain.de> wrote: > I have the exact same problem as the guy here: > > http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201105.mbox/%3C3A2B3E42FCAA4BF496AE625426C5C6E4@Wurstsemmel%3E > > AFAICS he did not get an answer. Is this a known issue? What can I do > other than doing what copyField should do in my application? > > I am using solr 4.0.0. > > Thanks, > > Robert
