That would work too.
You could always introduce a new method on the interface that
can accommodate a long and deprecate the existing one. That would not break
backward compatibility. I doubt the database would break since it already
supports 64 bit indexes.
Converting the long to its hex equivale
If you need an index on a 64-bit value, you can get creative and store the
64-bit number as the hex representation of your 64-bit value in a binary
index. Seems to me that a bit of lateral thinking is easier than a breaking
change in either a database client or, worse, a database itself.
Example:
Bumping this thread back up. Can someone from Basho take a shot at this ?
Thanks
-Deepak
On Wed, Dec 5, 2012 at 6:10 PM, Deepak Balasubramanyam <
deepak.b...@gmail.com> wrote:
> Hi folks,
>
> I have a query regarding riak indexes. My current understanding is that
> riak cannot index numbers who
