You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2011/04/12 21:38:05 UTC
[jira] [Commented] (LUCENE-3024) If index has more than
Integer.MAX_VALUE terms, seeking can it AIOOBE due to long/int overflow
[ https://issues.apache.org/jira/browse/LUCENE-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019003#comment-13019003 ]
Michael McCandless commented on LUCENE-3024:
--------------------------------------------
Fixed in 3.2, 4.0.
I'm leaving this open in case we ever release 3.1.1.
> If index has more than Integer.MAX_VALUE terms, seeking can it AIOOBE due to long/int overflow
> ----------------------------------------------------------------------------------------------
>
> Key: LUCENE-3024
> URL: https://issues.apache.org/jira/browse/LUCENE-3024
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 3.1.1, 3.2, 4.0
>
> Attachments: LUCENE-3024.patch
>
>
> Tom hit a new long/int overflow case: http://markmail.org/thread/toyl2ujcl4suqvf3
> This is a regression, in 3.1, introduced with LUCENE-2075.
> Worse, our Test2BTerms failed to catch this, so I've fixed that test to show the failure.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org