[ https://issues.apache.org/jira/browse/SOLR-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615122#action_12615122 ]
Ryan McKinley commented on SOLR-614: ------------------------------------ If I understood the discussion on the dev list properly, we would put off any syntax changes until 2.0, and then hopefully use some configuration standards that we don't maintain (spring) http://www.nabble.com/lesser-noise-in-solrconfig.xml-td18253180.html#a18253180 Yes, the new format is cleaner and more clear, but I fear compatibility/clarity issues with existing 1.x setups and multiple syntaxs for the same thing seems problematic. I think we should mark this as "won't fix", and save the configuration cleanup till we can do it well -- ie, spring. > 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 > > > 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.