So “lowercase” is, indeed, a solr.TextField, which is ineligible for docValues. Given that definition, the difference will be that a “string” type is totally un-analyzed, so the values that go into the index and the query itself will be case-sensitive. You’ll have to pre-process both to do the right thing.
> On Nov 9, 2019, at 6:15 PM, Antony Alphonse <antonyaugus...@gmail.com> wrote: > > Hi Shawn, > > Thank you. I switched the fieldType=string and it worked. I might have to > check on the use-case to see if "string" will work for us. > > I have noted the "lowercase" field type which I believe is similar to the > one in schema ver 1.6. > > > <fieldType name="lowercase" class="solr.TextField" > positionIncrementGap="100"> > <analyzer> > <tokenizer > class="solr.KeywordTokenizerFactory" /> > <filter class="solr.LowerCaseFilterFactory" > /> > </analyzer> > </fieldType> > > Thanks, > Antony > > On Sat, Nov 9, 2019 at 7:52 AM Erick Erickson <erickerick...@gmail.com> > wrote: > >> We can’t answer whether you should change the field type for two reasons: >> >> 1> It depends on your use case. >> 2> we don’t know what the field type “lowercase” does. It’s composed of an >> analysis chain that you may have changed. And whatever config you are using >> may have changed with different releases of Solr. >> >> Grouping is generally done on a docValues-eligible field type. AFAIK, >> “lowercase” is a solr-text based field so is ineligible for docValues. I’ve >> got to guess here, but I’d suggest you start with a fieldType of “string”, >> and enable docValues on it. >> >> Best, >> Erick >> >> >> >>> On Nov 9, 2019, at 12:54 AM, Antony Alphonse <antonyaugus...@gmail.com> >> wrote: >>> >>>> >>>> Hi Shawn, >>>> >>> >>> I will try that solution. Also I had to mention that the queries that >> fail >>> with this error has the "group.field":"lowercase". Should I change the >>> field type? >>> >>> Thanks, >>> Antony >> >>
