Thanks Shawn for your response!
Yes, we are on our way to indexing clients to SolrCloud 8 (and soon 9). We
have a massive Solr 6 deployment and it will take some time and so Solr 6
maintenance is still part of our job. We had not seen this error, but
recently a client complained of search failures and this was the underlying
cause.
Initially I was puzzled as I did not believe much had changed. What
revealed the problem was the combination of the user using this sort field
and searching way back on historical Solr 6 cores where an index problem
was lying yet to be revealed. I looked at the history of the schema
(before my time at this company), and indeed sortableSender and another
field were previously set to have docValues=true, and then changed to off.
It made us wonder if this change was handled properly in terms of taking
care of the index. We plan to kick off a re-index for the core but also
wondered if we needed to take further action. Your email confirms that we
should delete the index (and files/dirs) before re-indexing.
Thanks again,
Matt
On Mon, Jun 12, 2023 at 12:28 PM Shawn Heisey <apa...@elyograg.org> wrote:
> On 6/12/23 10:24, mtn search wrote:
> > Any tips as to why this error is occurring? Occurs with query when
> sorting
> > on sortableSender or other fields with docvalues set to false. Plan to
> > re-index, but would like to better understand this issue. Why would it
> > expect "=SORTED" when docvalues is set to false?
> >
> > <field name="sortableSender" type="icuCollationDefault" indexed="true"
> > stored="true" multiValued="false" required="false" docValues="false" />
> >
> > Solr version 6.4.2
> > <luceneMatchVersion>6.4.0</luceneMatchVersion>
> >
> > *error":{ "msg":"unexpected docvalues type NONE for field
> 'sortableSender'
>
> You realize that Solr 6.x is completely end of life, right? For a long
> time now.
>
> Why are you turning docValues off on a field that you want to use for
> sorting? docValues make sorting a LOT faster. It is possible that 6.x
> is assuming that a field used for sorting has docValues, but I am
> thinking it might be another problem:
>
> Did you ever have docValues defned for this field? If so, did you
> completely wipe the index and rebuild it after you changed the docValues
> setting? If you change just about anything on a field that has
> docValues, completely deleting the index directories using that schema
> and rebuilding the index from scratch is required. This is a
> requirement baked into Lucene, it doesn't come from Solr. f you don't
> do this, then you get docValues errors.
>
> Thanks,
> Shawn
>
