Terms query does not do analysis chain, but expect tokenized values.
Because it matches what is returned by faceting.
So I would check whether that field is string or text and difference in
processing. Enabling debug will also show difference in final expanded
form.
Regards,
Alex
P. S. It is
Alexandre Rafalovitch wrote
> What about copyField with the target being index only (docValue only?) and
> no lowercase on the target field type?
>
> Solr is not a database, you are optimising for search. So duplicate,
> multi-process, denormalise, create custom field types, etc.
>
> Regards,
>
What about copyField with the target being index only (docValue only?) and
no lowercase on the target field type?
Solr is not a database, you are optimising for search. So duplicate,
multi-process, denormalise, create custom field types, etc.
Regards,
Alex
On Wed., Feb. 3, 2021, 4:43 p.m.
Alexandre Rafalovitch wrote
> It is documented in the reference guide:
> https://lucene.apache.org/solr/guide/8_8/analysis-screen.html
>
> Hope it helps,
>Alex.
>
> On Tue, 2 Feb 2021 at 00:57, elivis
> elivis@
> wrote:
>>
>> Alexandre Rafalovitch wrote
>> > Admin UI also allows you to
It is documented in the reference guide:
https://lucene.apache.org/solr/guide/8_8/analysis-screen.html
Hope it helps,
Alex.
On Tue, 2 Feb 2021 at 00:57, elivis wrote:
>
> Alexandre Rafalovitch wrote
> > Admin UI also allows you to run text string against a field definition to
> > see what
Alexandre Rafalovitch wrote
> Admin UI also allows you to run text string against a field definition to
> see what each stage of analyzer chain does.
Thank you. Could you please give me some pointers how to achieve this (see
what each stage of analyzer chain does in Admin UI)?
--
Sent from:
Alexandre Rafalovitch wrote
> Admin UI also allows you to run text string against a field definition to
> see what each stage of analyzer chain does.
Thank you. Could please let me know how to do this (see what each stage of
analyzer chain does)?
--
Sent from:
Check the field type and associated indexing chain in managed-schema of
your core. It probably has the lowercase filter in it.
Find a better type or make one yourself. Remember to reload the schema and
reindex the content.
Admin UI also allows you to run text string against a field definition to
I'm using Terms Component functionality
(https://lucene.apache.org/solr/guide/8_4/the-terms-component.html) to get
all terms from an index. However, I need the terms to be in the original
case lettering (e.g. "TeSt"). So far I am only able to get lowercased terms
(i.e. "test" instead of "TeSt").