How about a warning section in Admin UI that shows possible issues with the configuration.
Could start with something absolutely basic like missing default field (we can detect that from configuration, right?) but I am sure there are other issues we could think of. Regards, Alex. Personal website: http://www.outerthoughts.com/ Current project: http://www.solr-start.com/ - Accelerating your Solr proficiency On Thu, Jun 5, 2014 at 11:48 PM, Erick Erickson <erickerick...@gmail.com> wrote: > 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 > thoughts. > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
