Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <323550485.1260797958287.JavaMail.jira@brutus>
Date: Mon, 14 Dec 2009 13:39:18 +0000 (UTC)
From: "Mark Miller (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1621) Allow current single core deployments
 to be specified by solr.xml
In-Reply-To: <2063388127.1259900720764.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mark Miller commented on SOLR-1621:
-----------------------------------

bq. The patch looks fine . I plan to commit it soon

I still think we need to do something about handleAliasAction - possibly just remove it. It's not really a deprecation like it says - if someone overrode it, its no longer called. Better to get a hard error.

> Allow current single core deployments to be specified by 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
>            Assignee: Noble Paul
>             Fix For: 1.5
>
>         Attachments: SOLR-1621.patch, SOLR-1621.patch, SOLR-1621.patch, SOLR-1621.patch, SOLR-1621.patch, SOLR-1621.patch, SOLR-1621.patch, SOLR-1621.patch, SOLR-1621.patch
>
>
> 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.