lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1722) Allowing changing the "special" default core name, and as a default default core name, switch to using collection1 rather than DEFAULT_CORE
Date Tue, 26 Jan 2010 16:56:35 GMT

    [ https://issues.apache.org/jira/browse/SOLR-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805093#action_12805093
] 

Mark Miller commented on SOLR-1722:
-----------------------------------

Right - the issue with cloud was that if you ask for the core name, it's known as "" rather
than its "other" name.

So their are def advantages to doing this in the dispatch filter - you can use the non ""
name and you can get rid of all the normalization going on in core container - 

the problem is back compat I think - if we just normalize in the DispatchFilter, anyone counting
on getting the default core with getCore("") now will have their code broken.

> Allowing changing the "special" default core name, and as a default default core name,
switch to using collection1 rather than DEFAULT_CORE
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-1722
>                 URL: https://issues.apache.org/jira/browse/SOLR-1722
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Minor
>             Fix For: 1.5
>
>         Attachments: SOLR-1722.patch
>
>
> see http://search.lucidimagination.com/search/document/f5f2af7c5041a79e/default_core

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message