Can you provide the full stack trace, and any details of what you
were doing when you tripped that assert?
Another thing to try is to run the org.apache.lucene.index.CheckIndex
tool (new in 2.3) to check your 2.2 index. It's possible your 2.2
index has some undetected corruption which this new assert is detecting.
Mike
Sergey Kabashnyuk wrote:
> Hi
> I want to update from lucene 2.2.0 to 2.3.0
> but I have assert it TermInfosWriter line 143.
>
> What is it mean
> assert compareToLastTerm(fieldNumber, termText, termTextStart,
> termTextLength) < 0 || (isIndex && termTextLength == 0 &&
> lastTermTextLength == 0);
>
> Can you help me?
>
> Sergey Kabashnyuk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
java-user-unsubscribe@...
> For additional commands, e-mail:
java-user-help@...
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
java-user-unsubscribe@...
For additional commands, e-mail:
java-user-help@...
