On 3/11/2015 4:45 PM, shamik wrote: > <field name="DocumentType" type="string" indexed="true" stored="true" > multiValued="false" required="false" omitNorms="true" docValues="true" > /> 3/11/2015, 2:14:30 PM ERROR SolrDispatchFilter > null:java.lang.IllegalStateException: unexpected docvalues type NONE > for field 'DocumentType' (expected=SORTED). Use UninvertingReader or > index with docvalues. null:java.lang.IllegalStateException: unexpected > docvalues type NONE for field 'DocumentType' (expected=SORTED). Use > UninvertingReader or index with docvalues.
I admit right up front that I know very little about what might be happening here ... but I did have one idea. It could be completely wrong. Is it possible that you have an index that fits the following description? The field originally did not have docValues. You enabled docValues on the field in the schema, but there are index segments still in the index directory from *before* you changed the schema. If that sounds at all possible, then if you did not fully reindex, there would be segments with valid documents that do not have docValues. You should fully reindex and then optimize before upgrading. If you did fully reindex, but did not optimize, then there might be segments with *deleted* documents that do not have docValues ... and maybe 4.7 was fine with that but 5.0 isn't. Whenever I upgrade Solr, I always reindex from scratch, and often I will completely delete all the data directories. It takes longer, but then I know the index is 100% correct for the version and config I'm running. I'll reiterate that this whole idea could be 100% wrong. Thanks, Shawn
