On 4/7/2010 9:16 AM, Shawn Heisey wrote:
On 4/5/2010 8:12 PM, Chris Hostetter wrote:
what you cna do however, is have a distinct solrconfig.xml for each
core,
which is just a thin shell that uses XInclude to include big chunkcs of
frequently reused declarations, and some cores can exclude some of thes
includes. (ie: turn the problem inside out)
When I first read this, I didn't really understand it. Now that I am
trying to actually use XInclude, it makes sense, and the more I think
about it, the more I like the idea. Thank you!
Shawn
I'm having a problem with this idea. It seems that what you include
with XInclude can only be a single XML element, not "big chunks" as I
had hoped. If you have more than one, it dies. It took running it
through xmllint to figure out why, the Solr exception was not
informative. This will make it choke if included in a single file:
<requestHandler name="/update" class="solr.XmlUpdateRequestHandler" />
<requestHandler name="/update/javabin"
class="solr.BinaryUpdateRequestHandler" />
<requestHandler name="/analysis/document"
class="solr.DocumentAnalysisRequestHandler" />
<requestHandler name="/analysis/field"
class="solr.FieldAnalysisRequestHandler" />
<requestHandler name="/update/csv" class="solr.CSVRequestHandler"
startup="lazy" />
<requestHandler name="/admin/"
class="org.apache.solr.handler.admin.AdminHandlers" />
Is there any way with XML to group multiple elements for the purposes of
inclusion? Can solrconfig.xml handle multiple <config> elements, or
just the one?
Thanks,
Shawn
