On 7/17/2017 4:26 PM, tstusr wrote:
> We want to use a copy field as a source for another copy field or some kind
> of post processing of a field.
<snip>
> As an example imagine we have on species
>
> abies durangensis
> abies flinckii
>
> so, after post processing, we expect to have only
> abies
>
> which is a word in genus files
Let's say that you have this in your schema, and you index "Test Words"
(note the capital letters) in field a:
<copyField source="a" dest="b"/>
Let's say that the index analysis on field a has the whitespace
tokenizer, a lowercase filter, and a stopword filter with "test" in the
list. This means that the search terms for field a on that document
will only have "words" included.
You might be expecting field b to only receive "words" when it gets
copied from field a ... but this is NOT what happens. Field b receives
the original text sent to field a, which is "Test Words", including both
words and the uppercase letters.
I think that transitive copies *do* work, so that you can copy field a
to b, then field b to c, though I am not 100 percent sure about that.
If that does work, the end field in the chain is still going to receive
"Test Words" like you sent to field a.
Chaining analysis through copyField does not work.
Thanks,
Shawn
