[
https://issues.apache.org/jira/browse/SOLR-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617318#action_12617318
]
Ryan McKinley commented on SOLR-614:
------------------------------------
perhaps I'm missing something... where/how does this get rid of any XPath?
Within a NamedListInitalizedPlugin, the plugin writer does not have access to
the Node and can't use it anyway? The plugin writer just has access to a
NamedList.
What I see is that this modifies/augments how we parse NamedLists, adding two
key features:
1. <a>value</a> == <str name="a">value</str>
2. <node a="value" /> -- adds '@a'=value to the NamedList 'node'
Perhaps I'm just reluctant to muck with a format that despite its awkwardness
works, and is consistent across (most) plugins. To me it seems wrong that I
would need to initialize most things with: {code:xml}<lst name="defaults"><str
name="echoParams">explicit</str></lst>{code} but *perhaps* other plugins would
need:
{code:xml}<defaults echoParams="explicit" />{code} Yes, the latter is better
looking, but considering that folks are already forced to use the former, it
seems wrong (and asking for trouble) mix and match.
NamedList isn't an XML standard, but in 1.x we can't get rid of it, so I think
we should just deal with it consistently and in 2.x make sure we fix it.
> 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
>
>
> 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.
