[
https://issues.apache.org/jira/browse/SOLR-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621187#action_12621187
]
Yonik Seeley commented on SOLR-545:
-----------------------------------
I've not fully diciphered the dispatch filter, but my first thought was that
multi-core could always be there (no enabled/disabled).
The only difference could be in the DispatchFilter which if a core of name ""
exists, it uses paths w/o a core name and the other cores would be unreachable.
That would enable core reloading, etc, for the single-core scenario.
> remove MultiCore "default" core / cleanup DispatchHandler
> ---------------------------------------------------------
>
> Key: SOLR-545
> URL: https://issues.apache.org/jira/browse/SOLR-545
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Fix For: 1.3
>
> Attachments: SOLR-545-path-access.patch, solr-545.patch,
> solr-545.patch, solr-545.patch, solr-545.patch
>
>
> MultiCore should require a core name in the URL. If the core name is
> missing, there should be a 404, not a valid core. That is:
> http://localhost:8983/solr/select?q=*:* should return 404.
> While we are at it, we should cleanup the DispatchHandler. Perhaps the best
> approach is to treat single core as multicore with only one core? As is the
> tangle of potential paths is ugly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
