Hi Russell,
Thank you for the code, it worked like a charm.
Warm regards,
Bryce
On 01/23/2014 11:59 PM, Russell Brown wrote:
Hi Bryce,
Sorry about this, and thanks for the detailed info. I do need to add MapReduce
friendly functions.
On 23 Jan 2014, at 23:51, Bryce Verdier wrote:
Thank
Hi Bryce,
Sorry about this, and thanks for the detailed info. I do need to add MapReduce
friendly functions.
On 23 Jan 2014, at 23:51, Bryce Verdier wrote:
> Thank you both Eric & Russeli for the answer, sadly it leads to more
> questions. Regardless of the type (though I can say in this case
Thank you both Eric & Russeli for the answer, sadly it leads to more
questions. Regardless of the type (though I can say in this case the
counters were pushed from the python 2.0.2 client, so I assume its
riak_dt_pncounter)
I get this error:
{"phase":0,"error":"badarg","input":"{ok,{r_object,<
On 23 Jan 2014, at 20:51, Eric Redmond wrote:
> For version 1.4 counters, riak_kv_pncounter. For 2.0 CRDT counters,
> riak_dt_pncounter.
As in, if the data was written in 1.4, or in 2.0 using the legacy, backwards
compatible 1.4 API endpoints, the the type is risk_kv_pncounter. If the counter
For version 1.4 counters, riak_kv_pncounter. For 2.0 CRDT counters,
riak_dt_pncounter.
Eric
On Jan 23, 2014, at 3:44 PM, Bryce Verdier wrote:
> In 1.4 there was just the simple function riak_kv_counters:value. In 2.0 I
> found the riak_kv_crdt module, which has a value function in it. But I'm
In 1.4 there was just the simple function riak_kv_counters:value. In 2.0
I found the riak_kv_crdt module, which has a value function in it. But
I'm not sure what "type" to use for second value argument for a counter.
Can someone share that with me?
Thanks in advance,
Bryce
___
