HI Shawn, solr Documentation says docValues=true/false works for only few fields. will that work on Text field ?
Copy from the reference guide - DocValues are only available for specific field types. The types chosen determine the underlying Lucene docValue type that will be used. The available Solr field types are: StrField and UUIDField. If the field is single-valued (i.e., multi-valued is false), Lucene will use the SORTED type. If the field is multi-valued, Lucene will use the SORTED_SET type. If you have already indexed data into your Solr index, you will need to completely re-index your content after changing your field definitions in schema.xml in order to successfully use docValues. Any Trie* numeric fields and EnumField. If the field is single-valued (i.e., multi-valued is false), Lucene will use the NUMERIC type. If the field is multi-valued, Lucene will use the SORTED_SET type. Regards, Anil On 19 February 2016 at 08:49, Anil <anilk...@gmail.com> wrote: > Thanks Shawn. This really helps. we are using 4.10.3 now.. will look into > 5.4.1. Thanks. > > Regards, > Anil > > On 18 February 2016 at 20:04, Shawn Heisey <apa...@elyograg.org> wrote: > >> On 2/18/2016 7:12 AM, Anil wrote: >> > Thank you, i just checked in 5.1. >> > >> > as facet fields has to be Strings and cannot be tockenized. is there any >> > way to search on case insensitive search on this field (not in a facet >> > filter scenario). >> >> If you configure docValues on the field in schema.xml and reindex, then >> the returned facets will be the original input values even if the field >> is tokenized, just as if you had used a string type without docValues. >> This should allow you to use one field for queries *and* facets. >> >> The reindex *is* required after adding docValues, and the index will be >> larger. >> >> Note that using 5.1 isn't recommended at this point. You should use the >> latest version available. Currently that's 5.4.1, but soon it will be >> 5.5. >> >> Thanks, >> Shawn >> >> >
