lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry Kan <solrexp...@gmail.com>
Subject Re: [solr 3.4.1] collections: meaning and necessity
Date Tue, 16 Jul 2013 11:28:07 GMT
Sorry, hit send too fast..

picking up:

from the answer by Jayendra on the link, collections and cores are the same
thing. Same is seconded by the config:

  <cores adminPath="/admin/cores" defaultCoreName="collection1"
host="${host:}" hostPort="${jetty.port:8983}"
hostContext="${hostContext:solr}"
zkClientTimeout="${zkClientTimeout:15000}">
    <core name="collection1" instanceDir="." />
  </cores>

we basically define cores.

We have a plain {frontend_solr, shards} setup with solr 3.4 and were
thinking of starting off with it initially in solr 4. In solr 4: can one
get by without using collections = cores?

We also don't plan on using SolrCloud at the moment. So from our standpoint
the solr4 configuration looks more complicated, than that of solr 3.4. Are
there any benefits of such a setup for non SolrCloud users?

Thanks,

Dmitry



On Tue, Jul 16, 2013 at 2:24 PM, Dmitry Kan <solrexpert@gmail.com> wrote:

> Hello list,
>
> Following the answer by Jaendra here:
>
>
> http://stackoverflow.com/questions/14516279/how-to-add-collections-to-solr-core
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message