: Additionally to the copy field, I need to add the destination field (in : the JSON API, with "add-field") to not give it its default attribute : values. : : I wonder why it is working for another schema without doing so, but : nevertheless, it's working now.
Because... : On the development, the same query throws an error, but not so ond the productive system. : * : The development system's index is version 1.7, whilst the productive system's index is version 1.6. And the difference between schema version 1.7 and 1.6 is... https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html#schemaversion-upgraded-to-1-7 > The default schemaVersion is now 1.7. With the new schema version, most > fields and fieldTypes that support docValues will have docValues enabled > by default. See the Enabling Doc Values Section for a complete list. > > Also, fields will be unable to be uninverted by default. > (uninvertible=false) You still haven't told us what the definition (either explicit, or implicit due to dynamicField) is for the field you were trying to sort on (title_s_lower) and the defintion of it's fieldType. I'm going to guess that it's a TextField so it implicitly has docValues=false in both schema version=1.6|1.7, and was sortable using the schema with version=1.6 because of the implicit uninvertible=true. (Where as with schema version=1.7 there is an implicit uninvertible=false) -Hoss http://www.lucidworks.com/
