I enjoy using collection aliases in all client references, because that allows me to change the collection all clients use without updating the clients. I just move the alias. This is particularly useful if I’m doing a full index rebuild and want an atomic, zero-downtime switchover.
On 1/28/16, 6:07 AM, "Shawn Heisey" <apa...@elyograg.org> wrote: >On 1/28/2016 2:59 AM, vidya wrote: >> Hi >> >> Then what is the difference between collection aliasing and shards parameter >> mentioned in request handler of solrconfig.xml. >> >> In request handler of new collection's solrconfig.xml >> shards = >> http://localhost:8983/solr/collection1,http://localhost:8983/solr/collection1 >> I can query both data of collection1 and collection2 in new collection which >> is same as collection aliasing. >> >> Is my understanding correct ? If so, then what is the special characteristic >> of collection alaising. Please help me. > >Collection aliasing handles it completely automatically, no need to put >a shards parameter *anywhere*. That is the main difference. > >The shards parameter is the old way of doing distributed searches. >SolrCloud completely automates the process so that neither the admin nor >the user has to worry about it. Aliases are part of that automation. > >Thanks, >Shawn >
