[
https://issues.apache.org/jira/browse/SOLR-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786456#action_12786456
]
Uri Boness commented on SOLR-1621:
----------------------------------
In addition to the awareness I believe it's also consistent. Having two
deferent configuration mechanisms for single and multi-core eventually adds to
the complexity. A consistent directory layout and one single access point to
the configuration (that is, solr.xml) simplifies things - user don't need to
keep in their mind "oh... this is multi-core... so it uses this layout" or
"oh... it's only one core, so there is not solr.xml just this directory".
Instead they get a consistent view of the directory/configuration structure
whether the use multi-core or not.
Also note it also helps in developing tools for Solr as you don't need to deal
with different configurations types and scenarios.
Thinks of RDBMS's... MySQL for example. Imagine MySQL would come with a default
configuration of a single database. But when you wanted to add more databases,
you would have to change the directory structure somewhere, introduce a new
configuration file, and only then you would be able to add more databases. In
that respect, Solr can be seen RDBMS and Solr Core can be seen as a Database
within this RDBMS.
> Deprecate deployments w/o solr.xml
> ----------------------------------
>
> Key: SOLR-1621
> URL: https://issues.apache.org/jira/browse/SOLR-1621
> Project: Solr
> Issue Type: New Feature
> Affects Versions: 1.5
> Reporter: Noble Paul
> Fix For: 1.5
>
>
> supporting two different modes of deployments is turning out to be hard. This
> leads to duplication of code. Moreover there is a lot of confusion on where
> do we put common configuration. See the mail thread
> http://markmail.org/message/3m3rqvp2ckausjnf
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
