lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos González-Cadenas (Commented) (JIRA) <>
Subject [jira] [Commented] (LUCENE-3298) FST has hard limit max size of 2.1 GB
Date Wed, 07 Dec 2011 17:32:41 GMT


Carlos González-Cadenas commented on LUCENE-3298:

Hello James,

Now we're using it and for the moment we haven't noticed any problems (although I must say
that we haven't done extensive testing). I'll let you know if we find any.

I haven't updated the patch to sync with the current trunk, I've just reverted to the appropriate
version of Lucene identified in the patch and then I've applied it there. If you have some
time, it would be great if you can sync the patch with the current trunk. 

As you suggest, I'll also take a look at the sections you mention to see if we can make it
more efficient.


> FST has hard limit max size of 2.1 GB
> -------------------------------------
>                 Key: LUCENE-3298
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: core/FSTs
>            Reporter: Michael McCandless
>            Priority: Minor
>         Attachments: LUCENE-3298.patch
> The FST uses a single contiguous byte[] under the hood, which in java is indexed by int
so we cannot grow this over Integer.MAX_VALUE.  It also internally encodes references to this
array as vInt.
> We could switch this to a paged byte[] and make the far larger.
> But I think this is low priority... I'm not going to work on it any time soon.

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