Default values vs non-existing keys for CRDTs

Hello, It seems that Riak Datatype API does not allow to distinguish between non-existing keys and default values. For example, if I query for non-existing key as follows: val fetchOp = new FetchCounter.Builder(key).build() val c = client.execute(fetchOp).getDatatype I'll get a counter that hold

Re: Default values vs non-existing keys for CRDTs

ak counter (or any other > data type) still exists as a regular object, and you can issue a HEAD > request to it (as opposed to a Fetch Counter or whatever), and it'll return > a 404 as expected. > > On Wed, Aug 19, 2015 at 8:59 PM, Timur Fayruzov > wrote: >

Re: Default values vs non-existing keys for CRDTs

;-1' at 'key' will result in 'key' with value 0, which is semantically different from answer "no 'key' found". Could you also comment whether null context for a set is a valid way to tell that set did not exist in store? It feels hacky. On 20 Aug 2015, at

Forming inputs to MR job

Hello, I'm trying to write a simple MR job using Javascript and hit a wall right at start. I can't figure out how to specify "inputs". Here's the code: curl -XPOST "my_riak_server:8098/mapred" -H "Content-Type: application/json" -d @-