lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <>
Subject Trappy behavior with default search field
Date Thu, 05 Jun 2014 16:48:52 GMT
We've all been bitten by the trappy problem with removing the "text" field
from schema.xml and then Solr failing to start b/c various handlers
specifically call it out.

Problem is that as people build out (particularly) SolrCloud clusters, this
innocent-seeming action is getting harder and harder to track down.

Is it worth a JIRA to address? And any clues how to address it? I started
thinking about in a _very_ superficial manner and I suspect that this is
one of those things that _seems_ easy but turns into a sticky wicket.

If we make sure and return a field that _is_ defined, then the problem
becomes even harder to detect. I mean you don't even get any warning but
don't find your docs b/c the default field isn't there and you're searching
on a different field than you think. At least the current behavior
sometimes causes Solr to not start at all.

Im not even sure it's worth doing, we currently both print an error in the
log and return an error message for a search, but wanted to gather other's

View raw message