tored (no
match on stored field doc_text...). Is there any way to make it highlighted
without also storing doc_text_morph field?
Thanks again...
Sent: Monday, June 08, 2020 at 3:39 PM
From: "Erick Erickson"
To: solr-user@lucene.apache.org
Subject: Re: Highlighting values of no
clusion was that 'hl.fl' param should be set to
> 'doc_text_lw' and it must be also stored...
>
>
>
>
> Sent: Tuesday, June 02, 2020 at 3:15 PM
> From: "Erick Erickson"
> To: solr-user@lucene.apache.org
> Subject: Re: Highlighting values of non stored fields
&g
method' param to 'unified' and 'fastVector' but no
luck either. My conclusion was that 'hl.fl' param should be set to
'doc_text_lw' and it must be also stored...
Sent: Tuesday, June 02, 2020 at 3:15 PM
From: "Erick Erickson"
To: solr-user@lucene.apache.org
Subject: Re: Highlighting val
Why do you think even variants need to be stored/highlighted? Usually
when you store variants for ranking purposes those extra copies are
invisible to the user. So most often people store exactly one copy
of a particular field and highlight _that_ field in the return.
So say my field is f1 and I
Our use case is as follow:
We are indexing free text documents. Each document contains metadata fields
(such as author, creation date...) which are kinda small, and one "big"
field that holds the document's text itself.
For ranking purpose each field is indexed in more then one "variation" and
