[
https://issues.apache.org/jira/browse/SOLR-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786343#action_12786343
]
Noble Paul commented on SOLR-1621:
----------------------------------
bq.continue supporting no solr.xml without deprecation. If a user is not going
to customize anything,
It is better to be consistent in the long run. There is no harm if the user
drops in this default solr.xml whether he customizes it or not. So , I believe
we should get rid of it 2 releases later.
bq.One of the minor issues is that the default page that shows all of the cores
doesn't care about aliases -
another thing I wish to change in this is we should store the aliases also in
the CoreDescriptor . That makes it simpler to show details.
It should show something like
Admin DEFAULT_CORE (alias :"" )
Admin core1 (alias : "c2","c3")
> 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.
