Re: Storing as erlang-binary/term, reading as json.

Haha.. Thanks for quick response. Now Its all clear. So I am going to tune my mapred jobs to work with content accordingly as well. Thanks heaps again, -f On Fri, Aug 12, 2011 at 4:46 AM, Jonathan Langevin < jlange...@loomlearning.com> wrote: > Thanks for the correction there Dan. Seems I need

Re: Storing as erlang-binary/term, reading as json.

Thanks for the correction there Dan. Seems I need to start responding... much more slowly, so you guys get in the correct answer before I speak :-) Cheers! * Jonathan Langevin Systems Administrator Loom Inc. Wilmington, NC: (910) 241-0433 - jlange...@loomlearning.co

Re: Storing as erlang-binary/term, reading as json.

The Accept header indicates what content-type your client is able to handle. When you specify "application/json" in the Accept header you are telling Riak to return the object if it's content-type is "application/json" otherwise return 406. http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec

Re: Storing as erlang-binary/term, reading as json.

I believe the Accept parameter is intended only for the ability to list riak-native data. So to get riak parameters back as json, that's when you specify the Accept header. Regarding objects that you store it Riak, my experience has been that it returns the data back as you stored it. So based on t