That cleared it up, thanks! Indeed, I was trying to add the index k/v as
regular meta in the headers.
On Mon, Jan 9, 2012 at 12:37 AM, Russell Brown wrote:
> Hi Daniel,
>
> On 9 Jan 2012, at 08:22, Daniel Rathbone wrote:
>
> I'm trying out 2i, and I'm having a little trouble similar to this old
Hi Daniel,
On 9 Jan 2012, at 08:22, Daniel Rathbone wrote:
> I'm trying out 2i, and I'm having a little trouble similar to this old
> thread. I don't see any keys returned when I try and query a secondary index.
>
> My storage_backend is set to riak_kv_eleveldb_backend. I seem to have added
I'm trying out 2i, and I'm having a little trouble similar to this old
thread. I don't see any keys returned when I try and query a secondary
index.
My storage_backend is set to riak_kv_eleveldb_backend. I seem to have
added values to the secondary index well enough - I can see a header
"X-Riak-
> you'll need to look in etc/app.config in the release directory and change
the value for the storage_backend setting to riak_kv_index_backend
Thanks.
How stable is the riak_kv_index_backend? If we're aiming to go to prod in a
couple months would we be better advised to use riak search? It seem
I believe 1.0 is scheduled for November.
---
Jeremiah Peschka
Founder, Brent Ozar PLF, LLC
On Aug 3, 2011, at 9:47 PM, Antonio Rohman Fernandez wrote:
> Another question... the old problem of querying smaller buckets with
> MapReduce is resolved with secondary indexes?
> following this pattern
Another question... the old problem of querying smaller buckets with MapReduce is resolved with secondary indexes?following this pattern => curl http://127.0.0.1:8098/buckets/loot/index/category_bin/eq/armor i think Riak doesn't have to check all the buckets/keys in memory to match the one you lo
seeing OSCON's PDF... when will we be able to have Riak 1.0 with
secondary indexes out? This is an improvement that can help me pretty
well out on my project. Any ETA?
thanks
Rohman
On Wed, 3 Aug 2011
22:02:53 -0600, Kelly McLaughlin wrote:
> Craig,
> The default
backend is bit cask and i
Craig,
The default backend is bit cask and if you want to use the indexes you'll need
to look in etc/app.config in the release directory and change the value for the
storage_backend setting to riak_kv_index_backend instead of
riak_kv_bitcask_backend. I suspect that's the problem. Cheers.
Kelly
