Also, this is particularly problematic because indices can't be negative so only 2^31 elements are actually possible.
On Wed, Jun 19, 2013 at 1:15 PM, Dan Filimon <[email protected]>wrote: > Hi everyone! > > The current Vector API only supports 32bit maximum indices for Vectors. > > I feel that 64bits would be more appropriate especially because the > indices are likely to be hash values of other data and 32bit will result in > quite a few collisions. > > Also, for some jobs, notably ItemSimilarityJob, this restriction means > that we need a special id to index map where we'll collide anyway. > > What do you think about adding support for 64bit indices? > Is anyone at all interested? >
