Solr basically does ONE thing (and related things) very well. Doing all the error messaging that yuou want would be fighting all the specialization builit into Solr/Lucene code.
Dennis Gearon Signature Warning ---------------- It is always a good idea to learn from your own mistakes. It is usually a better idea to learn from others’ mistakes, so you do not have to make them yourself. from 'http://blogs.techrepublic.com.com/security/?p=4501&tag=nl.e036' EARTH has a Right To Life, otherwise we all die. ----- Original Message ---- From: Jos Janssen <j...@websdesign.nl> To: solr-user@lucene.apache.org Sent: Tue, November 23, 2010 6:45:12 AM Subject: Re: SOLR and secure content The setup of multiple cores is a good option, thanks for the advice. I agree the "required" field should be in the application layer, but i also think some "error" handling should come from the Solr server to prevent incorrect usage. If i only knew how to do this for each request. Regards, Jos -- View this message in context: http://lucene.472066.n3.nabble.com/SOLR-and-secure-content-tp1945028p1953726.html Sent from the Solr - User mailing list archive at Nabble.com.
