The Luke Request Handler returns duplicate object keys in the JSON response
for multiValued fields. Only the last value survives the trip through a
decoder.
E.g. http://localhost:8983/solr/techproducts/admin/luke?show=doc&id=SP2514N
Snippet of the response:
"cat":{
"type":"string",
Hi,
I use only one solr instance. I want to use IndexUpgraderTool to migrate
from Solr 7.6 to 8.11.1. Is there any problem when migrating fields with
stored=false? Does "stored" have to be "true"?
Kind Regards,
Cihad Guzel
No, that is not a requirement. If the index was created in 7.6 you should
be fine. But do note that if the 7.6 index is a result of an upgrade from
an earlier version and you are now upgrading to 8.11.1, Lucene will not
allow you and the IndexUpgraderTool can't help you either.
-Rahul
On Sat, Feb
We used the solr Upgrader and were able to migrate from 5 to 6 to 7.
For example
java -cp lucene-core-7.7.3.jar:lucene-backward-codecs-7.7.3.jar
org.apache.lucene.index.IndexUpgrader -delete-prior-commits -verbose $index
After each migration we used the CheckIndex to confirm and indeed it reporte
Doing a full re-index into a clean solr 8 install is the recommended approach.
So if you have all fields stored (or docValues) and manage to dump complete
documents, then you should be all set.
You should be able to page through your entire index with ordinary &start= and
&rows= params, but if y
