You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2014/05/05 18:52:15 UTC
[jira] [Created] (SOLR-6042) Allow XInclude'ed config to have a top
level which gets stripped
David Smiley created SOLR-6042:
----------------------------------
Summary: Allow XInclude'ed config to have a top level <INCLUDE> which gets stripped
Key: SOLR-6042
URL: https://issues.apache.org/jira/browse/SOLR-6042
Project: Solr
Issue Type: Improvement
Reporter: David Smiley
Priority: Minor
The XInclude feature is pretty cool but it's limited to including a configuration element that has one top level tag. For example "<types>". That's a big limitation. This issue proposes that a special XML element of the name "INCLUDE" (or whatever) be allowed in a config file, which is stripped out when Solr reads the file. Solr would recursively check for elements of this name and if found then replace the node with all its children. In practice, nobody would use this except as a root of an XInclude'ed configuration fragment.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org