[
https://issues.apache.org/jira/browse/SOLR-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868374#comment-13868374
]
Benson Margulies commented on SOLR-5623:
----------------------------------------
Back to the exception decoration problem:
There's a general design puzzle here: an outer function knows something that an
inner function does not, and the catcher of the exception wants to know both. I
share your distaste for the obvious Java solution of endless exception
wrapping. Another option is to log, but does the Lucene code log things?
I'm working against trunk because I don't know any better. I'm inclined to stay
out at the Solr level for now, and maybe make another patch for this idea in
the core later.
> Better diagnosis of RuntimeExceptions in analysis
> -------------------------------------------------
>
> Key: SOLR-5623
> URL: https://issues.apache.org/jira/browse/SOLR-5623
> Project: Solr
> Issue Type: Bug
> Reporter: Benson Margulies
>
> If an analysis component (tokenizer, filter, etc) gets really into a hissy
> fit and throws a RuntimeException, the resulting log traffic is less than
> informative, lacking any pointer to the doc under discussion (in the doc
> case). It would be more better if there was a catch/try shortstop that logged
> this more informatively.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
