lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1621) Allow current single core deployments to be specified by solr.xml
Date Sat, 12 Dec 2009 04:14:18 GMT

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

Noble Paul commented on SOLR-1621:
----------------------------------

bq.You mark setSolrConfigFilename as deprecated, but it simply doesn't work anymore either
- thats not really deprecation. I feel that deprecating solrconfig-filename should be its
own issue so thats a more clear entry in CHANGES

I shall open another issue for this.  The setSolrConfigFilename() did not work for multicore
. So it does not make sense for us to bend over backwards to make it work in this and add
too many overloaded methods. Anyway, users won't need 



> 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
>             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.


Mime
View raw message