That'll work, but I would recommend you put an intermediate name in
there. It doesn't have to be "collection1", and it could even be
"solr", but I wouldn't put the conf, bin, and index directories as
immediate children of SOLR. You could do something like
SOLR
lib
solr
conf
data
Mostly, things are transitioning to "discovery-based" core enumeration
rather than solr.xml, and in the future your layout may cause you more
work.....
What do you gain by rearranging things like this? Unless there's a
tangible gain, I'm not sure it's worth the risk.
Best
Erick
On Mon, Jun 10, 2013 at 12:37 PM, bbarani <bbar...@gmail.com> wrote:
> Not sure if this is the right way,
>
> I just moved solr.xml outside of solr directory and made changes to sol.xml
> to make it point to solr directory and it seems to work fine as before. Can
> someone confirm if this is the right way to configure when running single
> instance of solr?
>
> <cores adminPath="/admin/cores" defaultCoreName="solr" host="${host:}"
> hostPort="${jetty.port:8983}" hostContext="${hostContext:solr}"
> zkClientTimeout="${zkClientTimeout:15000}">
> <core name="solr" instanceDir="solr" />
> </cores>
> </solr>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/How-to-ignore-folder-collection1-when-running-single-instance-of-SOLR-tp4069416p4069423.html
> Sent from the Solr - User mailing list archive at Nabble.com.
