Yes, that's a common strategy, and it's also fairly common to index two (or
more) versions of the field, with different tokenizations (or not
tokenized) if there is a need to perform different types of search the
field. This duplication can be acheived either with in the
schema, CloneFieldUpdateRe
Keeping the field as string so that no analysis is done on it has yielded
promising results.
I will test more tomorrow and report back.
-Original Message-
From: Hanjan, Harinder [mailto:harinder.han...@calgary.ca]
Sent: Wednesday, August 15, 2018 5:01 PM
To: solr-user@lucene.apache.