One other bit: There’s rarely a reason to, and multiple reasons _not_ to set stored=true for the _destination_ of a copyField, set it for the source field.
If you need to retrieve the original, just specify the source field in the fl list. Best, Erick > On Apr 24, 2020, at 8:42 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > > : Is what is shown in "analysis" the same as what is stored in a field? > > https://lucene.apache.org/solr/guide/8_5/analyzers.html > > The output of an Analyzer affects the terms indexed in a given field (and > the terms used when parsing queries against those fields) but it has no > impact on the stored value for the fields. For example: an analyzer might > split "Brown Cow" into two indexed terms "brown" and "cow", but the stored > value will still be a single String: "Brown Cow" > > > : So I indexed a document with "the quick brown fox jumped over the > : sleeping dog" set for stuff_raw and when I query for the document > : stuff_stems just has "the quick brown fox jumped over the sleeping > : dog" and NOT "quick brown fox jump over sleep dog" > > > https://lucene.apache.org/solr/guide/8_5/copying-fields.html > > Fields are copied before analysis is done, meaning you can have two > fields with identical original content, but which use different analysis > chains and are stored in the index differently. > > > > : Also stuff_everything only contains a single item, which is weird > : because I copy two things into it. > > https://lucene.apache.org/solr/guide/8_5/copying-fields.html > > Copying is done at the stream source level and no copy feeds into another > copy. This means that copy fields cannot be chained i.e., you cannot copy > from here to there and then from there to elsewhere. However, the same > source field can be copied to multiple destination fields: > > > -Hoss > http://www.lucidworks.com/
