We're having a debate internally on my team about the final format that we
should store our objects in Riak. Some are voting for protobuf (because we
use it pretty heavily in house) and i'm advocating for JSON or gzipped JSON
because i feel like it would be easier to traverse and analyze with the
j
I'm having trouble finding documentation for certain pieces of riak_core
code (and at times i'm not sure whether some concepts are OTP or Riak
defined) so I figured i'd ask here. I've mostly been using try-try-try,
bash_banjo, and riak_kv as my guides.
Once i know the answers and understand I woul
Hey all,
i'm having trouble articulating for colleagues why using vnode_vclock=true
in Riak 1.0 avoids the issues outlined in the Vector Clocks are Hard page.
This is probably a sign that i don't understand it well enough myself.
My understanding is that requests to a vnode are processed in seria
What is the best way for a riak_core app to use riak_kv for persistent
storage? I thought that riak search did this but haven't found it in
that code yet. Should I use the erlang interface via http or protobuf
or is there an API or module I can use since my app is running as a
member of the cluster
Thank Ryan!
There's a funny side-effect with posting on a user list or going to ask
somebody for help with something where as soon as you do it, you find the
answer you were looking for :) I found riak:local_client() shortly after I
posted and it's working like a charm.
thanks again!
Adam
On Mo
ec and manage the two
> separately.
> Not knowing details of your application, I cannot really comment any
> further, but I thought I'd bring this to your attention.
>
> Mihai
>
> On Mar 6, 2012, at 6:59 AM, Adam Schepis wrote:
>
> Thank Ryan!
>
> There's
