[
https://issues.apache.org/jira/browse/SOLR-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615146#action_12615146
]
Noble Paul commented on SOLR-614:
---------------------------------
The scope of this bug is not same as
http://www.nabble.com/lesser-noise-in-solrconfig.xml-td18253180.html#a18253180
I descoped it.
It *WILL NOT* make any changes to the _solrconfig.xml_. The intend is to enable
new components to take advantage of a flexible format. When I say new
components the components written by users after 1.3 (intended to run on top of
1.3)
We use our own custom components in our organization. I am sure there are a lot
of other users who do that. There is no harm in enabling them to choose their
format (if they wish to do so)
If we plan to change the configuration in any which way in the future , how can
this affect any of our plans?
The implementation does not have to be the same (or even the scope) . But we
should allow more flexibility in the API for component writers
> 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.
