You can also use a dynamic field as the destination. So with the
configuration below, if your document had a field 'foo_ss' it would create
a 'foo_facets'
< dynamicField name="*_facets" type="string" indexed="true" stored="true"
required="false" multiValued="true" />
- Andy -
On Thu, Feb 2, 20
Yes, you should be able to use a dynamicField as the source. That's really
just a shorthand to keep you from having to enumerate all possible field
names in the schema. I don't think order matters, but I tend to put
copyField directives after all the field and dynamicField definitions, for
readab
• castr...@slhs.org<mailto:x...@slhs.org>
From: Jeremy Buckley - IQ-C
Sent: Thursday, February 2, 2023 4:16 PM
To: users@solr.apache.org
Subject: Re: facet.field reported as individual words and not the complete
string
The culprit here is text_general. Your
The culprit here is text_general. Your field is getting tokenized at index
time, and each token gets returned as a facet value. Fields that you plan
to use for faceting (or sorting) should be string or some numeric type.
Common practice is to define a second field of type string and use a
copyFie
Hello community, thank you for taking the time to read my question. Your
insights are most appreciated.
I am making queries utilizing the facet.field parameter. The field I provide is
multivalued. It is indexed using a dynamic field:
It is indexed in with the name "facets_ss".
The values are of
