This file lists Solr's raw release notes with details of every change to Solr. Most people will find the solr-upgrade-notes.adoc file more approachable. https://github.com/apache/solr/blob/main/solr/solr-ref-guide/modules/upgrade-notes/pages/solr-upgrade-notes.adoc
./server/scripts/cloud-scripts/zkcli.sh -zkhost 127.0.0.1:2181 -cmd clusterprop -name legacyCloud -val true
To migrate your existing solrconfig.xml, you can replace elements as follows:
<!-- TieredMergePolicy example --> <!-- deprecated --> <mergeFactor>??</mergeFactor> <mergePolicy class="org.apache.lucene.index.TieredMergePolicy"> <bool name="useCompoundFile">???</bool> <!-- deprecated since Lucene/Solr 4.4.0 --> ... </mergePolicy> <!-- replacement --> <useCompoundFile>???</useCompoundFile> <!-- since Lucene/Solr 4.4.0 --> <mergePolicyFactory class="org.apache.solr.index.TieredMergePolicyFactory"> <int name="maxMergeAtOnce">??</int> <!-- formerly the <mergeFactor> element implicitly set this --> <int name="segmentsPerTier">??</int> <!-- formerly the <mergeFactor> element implicitly set this --> ... </mergePolicyFactory>
<!-- Log(ByteSize|Doc)MergePolicy example --> <!-- deprecated --> <maxMergeDocs>????</maxMergeDocs> <mergeFactor>??</mergeFactor> <mergePolicy class="org.apache.lucene.index.Log?MergePolicy"> <bool name="useCompoundFile">???</bool> <!-- deprecated since Lucene/Solr 4.4.0 --> ... </mergePolicy> <!-- replacement --> <useCompoundFile>???</useCompoundFile> <!-- since Lucene/Solr 4.4.0 --> <mergePolicyFactory class="org.apache.solr.index.Log?MergePolicyFactory"> <int name="maxMergeDocs">????</int> <!-- formerly the <maxMergeDocs> element set this --> <int name="mergeFactor">??</int> <!-- formerly the <mergeFactor> element set this --> ... </mergePolicyFactory>
Additional Work:
Additional Work:
Example: The following two documents will be indexed to the same shard since they share the same domain "customerB!".
{"id" : "customerB!doc1" [...] }
{"id" : "customerB!doc2" [...] }>
At query time, one can specify a "shard.keys" parameter that lists what
shards the query should cover.
http://.../query?q=my_query&shard.keys=customerB!
Collections that do not specify numShards at collection creation time
use custom sharding and default to the "implicit" router. Document updates
received by a shard will be indexed to that shard, unless a "_shard_" parameter
or document field names a different shard.
(Michael Garski, Dan Rosher, yonik)
Additional Work:
Additional Work:
Additional Work:
Additional Work:
Behavior changes from the previous version: