lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Assigned] (SOLR-3753) Core admin and solr.xml documentation for 4.0 needs to be updated for 4.0 changes
Date Sat, 08 Sep 2012 00:39:08 GMT


Hoss Man reassigned SOLR-3753:

    Assignee: Hoss Man
> Core admin and solr.xml documentation for 4.0 needs to be updated for 4.0 changes
> ---------------------------------------------------------------------------------
>                 Key: SOLR-3753
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.0-BETA
>            Reporter: Tom Burton-West
>            Assignee: Hoss Man
>             Fix For: 4.0
> The existing documentation on Solr Cores needs to be updated to reflect changes in Solr
> If having at least one solr core declared is mandatory for Solr 4.0, that needs to be
stated in the release notes, in the example solr.xml file, and on the wiki page for CoreAdmin.
> In the absence of a solr.xml file, current 4.0 behavior is to use defaults declared in  This needs to be documented; probably in solr.xml and/or on the CoreAdmin
page.  (See line 94 of where the default name "collection1" is declared.  Without
this documentation, users can get confused about where the "collection1" core name is coming
from. (I'm one of them).
> The solr.xml file states that paths are relative to the "installation directory" This
needs to be clarified.  In addition it appears that currently relative paths specified using
"." or ".." are interpreted as string literals.  If that is not a bug, than this behavior
needs to be documented.  If it is a bug, please let me know and I'll open another issue.
> The  example/solr/README.txt  Needs to clarify which files need to be in Solr Home and
which files are mandatory or optional in the directories containing configuration files (and
data files) for Solr cores.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message