[
https://issues.apache.org/jira/browse/SOLR-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868354#comment-13868354
]
Robert Muir commented on SOLR-5623:
-----------------------------------
Benson I don't know about that, its pretty tricky.
Especially this particular place in the code, I think we should keep as simple
as possible and not be messing with such exceptions. There is already plenty
complexity here (aborting vs non-aborting exceptions) and so on for lucene to
deal with.
In general whats happening here is not happening inside indexwriter, its
happening in the analysis chain. I think solr or other applications is the
right place to add additional debugging information (such as a unique ID for
the document) because only it has that additional context to ensure its what is
useful to get to the bottom.
> 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: [email protected]
For additional commands, e-mail: [email protected]
