Yes, all the three options (copy fields, using dynamic fields and the
SortableTextField) are feasible. Since I am on the 7.5.0 version of Solr, I
will go ahead with the SortableTextField option.
Thank you team!!
On Fri, Dec 7, 2018 at 8:46 PM Alexandre Rafalovitch
wrote:
> If you are on the
If you are on the latest Solr (7.3+), try switching from TextField to
SortableTextField in your string_ci definition above.
That type implicitly uses docValues and should return original text
for faceting purposes, while still allowing analyzers.
Regards,
Alex.
On Thu, 6 Dec 2018 at 08:26,
you could change your indexer to index the values to a dynamic field *_ci
for each of the facets.
ie, your facet is organization. index to the string field, and also index
it to the dynamic organization_ci field
but there will not be a short cut way of doing this in the schema itself
On Fri,
Fields need to be copied. You can shorten the schema with using wildcards
*.
On Fri, Dec 7, 2018 at 9:03 AM Ritesh Kumar
wrote:
> Yes, it can be used.
> But, what if I have other such facets on different other fields. Use of
> copyField will require me to create a dedicated copy field for each
Yes, it can be used.
But, what if I have other such facets on different other fields. Use of
copyField will require me to create a dedicated copy field for each such
facet.
I want to know if there is any other option where I do not have to add
multiple copy fields.
On Thu, Dec 6, 2018 at 7:06 PM
Hello, Ritesh.
It's obviously done with copyField.
On Thu, Dec 6, 2018 at 4:26 PM Ritesh Kumar
wrote:
> Hello team,
>
> I am trying to prepare facet on a field of type string. The facet data will
> be shown according to the user's query on this very field.
>
> required="false"
Hello team,
I am trying to prepare facet on a field of type string. The facet data will
be shown according to the user's query on this very field.
As this field is of type string, it works fine with case sensitive query. I
want to be able to query on this field irrespective of the case.
I
