On Tue, Jan 22, 2013 at 12:23 PM, Meng Muk <meng....@uniqueinteractive.com> wrote:
> If I set the field type to "text_en" however it works, I'm guessing > something in the way the text is being analyzed is causing this exception > to appear? Is there a limitation in how storeOffsetsWithPositions should be > used? > IndexWriter will refuse broken offsets up-front if you use this feature: Its strict about this and will throw an exception at index-time if the analyzer is broken. You can see the list of broken analysis components here: https://issues.apache.org/jira/browse/LUCENE-4641 If you really want to use one of these broken analysis components, you can use another highlighter, but it probably just means you wont see these analyzer bugs until search time (InvalidTokenOffsetsExceptions and so on)
