d, 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.
> >
> &g
e. 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
>
> 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
Hi,
I shared the collection and re-indexed the data with the same schema. But
one of the field is throwing the below error. Any suggestions?
ERROR (qtp672320506-32) [c: s:shard3 r:core_node01 x:_shard3_replica_n69]
o.a.s.h.RequestHandlerBase java.lang.IllegalStateException: unexpected
docvalu
Hi,
I am trying to get some help on frequent OOME I am seeing in my collection.
I have a single shard with four replicas. Each replica runs on a 10G heap.
I have around 12 mil documents with size on disk around 15G. From the plot
below, it looks to me that full GC are taking longer time. I am look
