lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <>
Subject Re: Solr Config XML DTD's
Date Sun, 01 May 2011 11:56:14 GMT
If not a DTD, can we put some more "customized" form of validation for
Solr's configuration?

In general, I think servers should be anal on startup, refusing to
start if there's anything off in their configuration.

(Of course, along with this, the error messaging has to be *excellent*
so you know precisely where the problem is, what's wrong, how to fix

If you take the lenient/forgiving approach then you wind up with Solr
instances in unknown states -- the app developer thinks they turned X
on, everything starts fine, but then, silently, inexplicably, it's not
working.  This then leads to frustration, thinking Solr is buggy, not
using this feature, blogging about problems, etc.


On Tue, Mar 29, 2011 at 7:15 PM, Chris Hostetter
<> wrote:
> : Hi, this is my first post to the mailing list.  I'm working on a commercial
> Welcome!
> : My DTD works for our internal version of queryElevation.xml, but since the
> : ATTRIB name of the <doc/> tag could be anything, I'm not sure how to write a
> : DTD that would validate any valid query elevation file.
> right .. this is one of the reasons why we've never tried to publish a DTD
> for the solrconfig.xml or schema.xml files either.  there are lots of
> cases where plugins can define arbitrary attributes on the XML nodes.
> If i had the chance to do it all over again, and i better understood xml
> back when yonik first showed me what the configs would look like, i would
> have suggested using xml namespaces .. but that ship kind of sailed a
> while ago.
> we're getting a little better -- moving towards using the same type of
> "NamedList" backed XML for the initialization anytime new plugins are
> added, but i don't see it being feasible to have a config DTD anytime
> soon.
> -Hoss
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message