Shalin,

Why was this committed? There were numerous opinions suggesting otherwise that weren't addressed, including most recently on the Solr 1.3 release date thread. I think it should be rolled back until there is a consensus amongst the committers, which there does not appear to be.


-Grant

On Aug 6, 2008, at 11:06 AM, Shalin Shekhar Mangar (JIRA) wrote:


[ https://issues.apache.org/jira/browse/SOLR-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shalin Shekhar Mangar resolved SOLR-614.
----------------------------------------

   Resolution: Fixed

Committed revision 683288 after removing the attribute reading for plain NamedList so that existing usage is not changed in any way.

Thanks Noble!


Allow components to read any kind of XML from solrconfig
--------------------------------------------------------

               Key: SOLR-614
               URL: https://issues.apache.org/jira/browse/SOLR-614
           Project: Solr
        Issue Type: Improvement
  Affects Versions: 1.3
          Reporter: Noble Paul
          Assignee: Shalin Shekhar Mangar
          Priority: Trivial
           Fix For: 1.3

Attachments: SOLR-614.patch, SOLR-614.patch, SOLR-614.patch, SOLR-614.patch


All the components initialized by Solr have an init(NamedList args) initializer. This leads us to writing the configuration needed for the component in the NamedList xml format. People familiar with Solr may know the format but most of what is written is noise than information. For users who are not familiar w/ the format find it too difficult to understand why they have to write it this way. Moreover , it is not a very efficient way to configure .

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


--------------------------
Grant Ingersoll
http://www.lucidimagination.com

Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ







Reply via email to