[LUCENE-3976] Improve error messages for unsupported Hunspell formats

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: modules/analysis
• Lucene Fields: New
• Assignee: Chris Male
• Reporter: Chris Male
• Created: 12/Apr/12 09:12
• Updated: 28/Aug/22 13:14
• Resolved: 01/Jun/12 09:27

Description

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:

SFX CA 0 /CaCp

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 parse.