[
https://issues.apache.org/jira/browse/SOLR-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785791#action_12785791
]
Noble Paul edited comment on SOLR-1621 at 12/4/09 7:09 AM:
-----------------------------------------------------------
The proposed design.
Going forward for the single core example we will add a solr.xml to the
$SOLR_HOME/solr directory whose content will look like
{code:xml}
<?xml version="1.0" encoding="UTF-8" ?>
<solr persistent="false">
<cores adminPath="/admin/cores">
<!- "DEFAULT_CORE" is a special name . Solr will automatically create an
alias "" for this name-->
<core name="DEFAULT_CORE" instanceDir="." />
</cores>
</solr>
{code}
the core will be accessible by both the names
* http://host:port/solr/ ("" is an alias for DEFAULT_CORE )
* http://host:port/solr/DEFAULT_CORE
All coreadmin actions can be performed using the core name as DEFAULT_CORE. So
all coreadmin features will work for single core as well
For legacy users who have single core deployments no change needs to be done.
if the solr.xml is missing we will use a default solr.xml whose content is same
as above. So everything will be backward compatible. We can mark the
deployments w/o solr.xml as deprecated and the we can remove it completely
later.
was (Author: noble.paul):
The proposed design.
Going forward for the single core example we will add a solr.xml to the
$SOLR_HOME/solr directory whose content will look like
{code:xml}
<?xml version="1.0" encoding="UTF-8" ?>
<solr persistent="false">
<cores adminPath="/admin/cores">
<core name="DEFAULT_CORE" instanceDir="." />
</cores>
</solr>
{code}
the core will be accessible by both the names
* http://host:port/solr/ ("" is an alias for DEFAULT_CORE )
* http://host:port/solr/DEFAULT_CORE
All coreadmin actions can be performed using the core name as DEFAULT_CORE. So
all coreadmin features will work for single core as well
For legacy users who have single core deployments no change needs to be done.
if the solr.xml is missing we will use a default solr.xml whose conmtent is
same as above. So everything will be backward compatible. We can mark the
deployments w/o solr.xml as deprecated and the we can remove it completely
later.
> 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.
