You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Benson Margulies (JIRA)" <ji...@apache.org> on 2014/02/05 01:50:10 UTC

[jira] [Resolved] (SOLR-5623) Better diagnosis of RuntimeExceptions in analysis

     [ https://issues.apache.org/jira/browse/SOLR-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies resolved SOLR-5623.
------------------------------------

    Resolution: Fixed

> 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
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org