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

Ryan McKinley commented on SOLR-614:
------------------------------------

As i have said, I think consistency is a good thing and we will hopefully get 
out of the custom config format business in 2.0.  But I also see that having 
ugly configs makes it difficult to be clear about what it does.  (I remember 
struggling to figure out that lst != 1st)  Ugly configs are a big deal, so I 
hate to throw sticks at the endeavor...  I imagine any translation to a new 
format would involve reading it and then outputting the relevant configs rather 
then trying some sort of text manipulation.  With that in mind, it probably 
makes little difference on that front.

So I'll change my vote to -0, and I'll let you all sort out what should 
happen...



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

Reply via email to