Yep, we're not communication ;) Use the original source field for the genus, as:
<copyField source="attr_conten*" dest="species"/> <copyField source="attr_conten*" dest="genus"/> The difficulty here is that there might be false hits if the genera names happen to match words in the input that are not part of a genus/species pair. On Thu, Jul 20, 2017 at 9:55 AM, tstusr <ulfrhe...@gmail.com> wrote: > Well, correct me if I'm wrong. > > Your suggestion is to use species field as a source of genus field. We try > with this > > <copyField source="attr_conten*" dest="species"/> > <copyField source="species" dest="genus"/> > > Where species work as described and genus just use a KWF, like this: > > <fieldType name="genus_type" class="solr.TextField" > positionIncrementGap="0"> > <analyzer type="index"> > <tokenizer class="solr.StandardTokenizerFactory"/> > <filter class="solr.KeepWordFilterFactory" words="genus.txt" > ignoreCase="true"/> > </analyzer> > <analyzer type="query"> > <tokenizer class="solr.StandardTokenizerFactory"/> > <filter class="solr.LowerCaseFilterFactory"/> > </analyzer> > </fieldType> > > But now, the problem now is different. > > When we try the behavior in analysis section in solr provided UI it works as > expected. > > Nevertheless, when we use it at indexing time (When we post pdf files, to > extractor) the field doesn't even appear. We think it's because the info > becomes from another copyField. > > Did I misunderstand your suggestion? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Copy-field-a-source-of-copy-field-tp4346425p4347013.html > Sent from the Solr - User mailing list archive at Nabble.com.
