I wonder if looking more directly at the indexes would allow you to get closer to the problem source.
Have you tried comparing/exploring the indexes with Luke? It is in the Lucene distribution (not Solr), and there is a small explanation here: https://mocobeta.medium.com/luke-become-an-apache-lucene-module-as-of-lucene-8-1-7d139c998b2 Regards, Alex. On Wed, 17 Feb 2021 at 16:58, Vivaldi <uyil...@vivaldi.net.invalid> wrote: > > I was getting “illegal argument exception length must be >= 1” when I used > significantTerms streaming expression, from this collection and field. I > asked about that as a separate question on this list. I will get the whole > exception stack trace the next time I am at the customer site. > > Why any other field in other collections doesn’t have that flag? We have > numerous indexed, non-indexed, docvalues fields in other collections but not > that row > > Sent from my iPhone > > > On 16 Feb 2021, at 20:42, Shawn Heisey <apa...@elyograg.org> wrote: > > > >> On 2/16/2021 9:16 AM, ufuk yılmaz wrote: > >> I didn’t realise that, sorry. The table is like: > >> Flags Indexed Tokenized Stored UnInvertible > >> Properties Yes Yes Yes Yes > >> Schema Yes Yes Yes Yes > >> Index Yes Yes Yes NO > >> Problematic collection has a Index row under Schema row. No other > >> collection has it. I was asking about what the “Index” meant > > > > I am not completely sure, but I think that row means the field was found in > > the actual Lucene index. > > > > In the original message you mentioned "weird exceptions" but didn't include > > any information about them. Can you give us those exceptions, and the > > requests that caused them? > > > > Thanks, > > Shawn >
