lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3976) Improve error messages for unsupported Hunspell formats
Date Fri, 01 Jun 2012 08:11:23 GMT


Chris Male commented on LUCENE-3976:

Hi Luca,

I'm unsure about this approach.  What other kind of Exceptions can be thrown other than IOExceptions?
I think we should explore what those possible errors are and fix them at their source, to
provide targeted Exceptions.  If there is a problem parsing, then we should thrown a ParseException
with the line number causing the problem.
> Improve error messages for unsupported Hunspell formats
> -------------------------------------------------------
>                 Key: LUCENE-3976
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: modules/analysis
>            Reporter: Chris Male
>         Attachments: LUCENE-3976.patch, LUCENE-3976.patch
> Our hunspell implementation is never going to be able to support the huge variety of
formats that are out there, especially since our impl is based on papers written on the topic
rather than being a pure port.
> Recently we ran into the following suffix rule:
> {noformat}SFX CA 0 /CaCp{noformat}
> Due to the missing regex conditional, an AOE was being thrown, which made it difficult
to diagnose the problem.
> We should instead try to provide better error messages showing what we were unable to

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message