[
https://issues.apache.org/jira/browse/SOLR-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892313#comment-13892313
]
ASF subversion and git services commented on SOLR-5623:
-------------------------------------------------------
Commit 1564834 from hoss...@apache.org in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1564834 ]
SOLR-5623: revert r1564739, shalin already fixed the bug that caused these
failures, but Uwe didn't know that (merge r1564831)
> Better diagnosis of RuntimeExceptions in analysis
> -------------------------------------------------
>
> Key: SOLR-5623
> URL: https://issues.apache.org/jira/browse/SOLR-5623
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.6.1
> Reporter: Benson Margulies
> Assignee: Benson Margulies
> Fix For: 5.0, 4.7
>
> Attachments: SOLR-5623-nowrap.patch, SOLR-5623-nowrap.patch
>
>
> 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
