If you only have one collection and no Solr cloud, then don't use solr.xml at all. It will automatically assume 'collection1' as a name.
If you do want to have some control (shards, etc), do not include the optional parameters you do not need. See example here: http://my.safaribooksonline.com/book/databases/9781782164845/1dot-instant-apache-solr-for-indexing-data-how-to/ch01s02_html You don't even need defaultCoreName attribute, if you are happy to always include core name in the URL. Regards, Alex. Personal website: http://www.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Tue, Jul 16, 2013 at 7:28 AM, Dmitry Kan <solrexp...@gmail.com> wrote: > 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 <solrexp...@gmail.com> wrote: > > > Hello list, > > > > Following the answer by Jaendra here: > > > > > > > http://stackoverflow.com/questions/14516279/how-to-add-collections-to-solr-core > > >
