On 30 Jan 2012, at 20:07, Dietrich Featherston wrote:
> Yeah I had something that I thought would work then ran into some assumptions
> about handling of the existing bin / int query types. Started to introduce a
> higher level Index type that a generic RangeQuery could operate on rather
> tha
Yeah I had something that I thought would work then ran into some
assumptions about handling of the existing bin / int query types. Started
to introduce a higher level Index type that a generic RangeQuery could
operate on rather than playing the combinatorics game with the existing
AbstractRangeQue
That's perfect thanks. I think I was presuming that the name of the
underlying index was $key_bin so this didn't cross my mind. Definitely
agree with having a separated typed KeyIndex rather than changing how
BinIndex or IntIndex work.
Thanks,
D
On Mon, Jan 30, 2012 at 10:41 AM, Russell Brown wr
On 30 Jan 2012, at 18:12, Dietrich Featherston wrote:
> I'm using a leveldb-backed riak 1.0.2 and looking for some suggestions to
> fetch a block of data by key range. I have control over the keys and all
> reads out of this setup will involve at minimum a key range. It seems that if
> leveldb
I'm using a leveldb-backed riak 1.0.2 and looking for some suggestions to
fetch a block of data by key range. I have control over the keys and all
reads out of this setup will involve at minimum a key range. It seems that
if leveldb is an ideal candidate for this kind of access pattern so long as
I
