[
https://issues.apache.org/jira/browse/SOLR-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616458#action_12616458
]
Shalin Shekhar Mangar commented on SOLR-614:
--------------------------------------------
I think the current scope is reasonable. This limited scope makes a cleaner
config possible but makes no changes to the public configuration as it stands
now. Future (Solr 1.4+) and custom user components can use the cleaner
configuration syntax if they choose to do so. We can document in the wiki that
a cleaner syntax is available for component writers if they so desire. Future
versions of the existing components which use the XPath based parsing
currently, can switch to using this code for a cleaner and consistent
implementation, if we so desire.
Thoughts?
> 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.
