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
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
On 6/5/2014 10:48 AM, Erick Erickson 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
In my view, solrconfig.xml shouldn’t refer to any field by name out of the
box, except for the /browse handler, and perhaps pre-filling the query form
in the admin GUI. That’s it.
A couple years ago at about the time I became a committer, I finally did
something about a feature I am very
