RangeValue does not support long numeric type, eg: -7989522793807773965

[jameycai]

RangeValue does not support long numeric. When does it support?

eg:

1. query 19 bit long numeric , Values.eg(-7989522793807773965)
2. query 13 bit milliseconds, Values.between(1531152000000, 1543507200000)

[gkorland]

Are you referring to a RangeValue?

[jameycai]

Yes!

[gkorland]

RediSearch currently supports up to 48bit values

[jameycai]

Values.eg (or Values.between), only supports int numeric type , don't supports long numeric type?

eg: -7989522793807773965

[gkorland]

The RediSearch server side is currently limited to double.
I opened a feature request on RediSearch see: RediSearch/RediSearch#557

[jameycai]

Thank you!

This restriction has been limited to use, such as query time in milliseconds, and 19-bit integer numerical queries. There are many usage scenarios.

[gkorland]

Is time the only case where you need 64bit long? We consider of adding a primitive Time type

[jameycai]

I usually convert time to 13-bit milliseconds for storage.

[jameycai]

Now, I use java UUID.randomUUID().getLeastSignificantBits() to produce long numeric Id.

[jameycai]

@gkorland Can you add this feature in the next version?