On 9/13/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
I agree in spirit, but the caveat to that is that if we silently work arround the problem at a very low level, it can lead to situations were lucene is constaintly waiting and retrying every single operation -- which may lead people to assume Lucene itself is slow just because of their environment.
Good point. In practice I think it's only a problem if it's reproducable (happens very often). I'd be surprised if it was that reproducable since lucene wouldn't be usable at all for some people if that were the case. A warning of some kind would seem to be most appropriate.
An exception thrown can be researched and documented in such a way that application developers can fix it themselves.
The problem is, it could be spurious enough that one wouldn't get the exception until it's in production, or sold to a customer, etc... too late to debug. It would be nice if we could handle the spurious error. -Yonik http://incubator.apache.org/solr Solr, the open-source Lucene search server --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
