keys=stream

Sean Cribbs sean at basho.com
Tue May 4 09:22:38 EDT 2010


This behavior is unchanged since its implementation in 0.8 or 0.9.  To better demonstrate what that statement means, here's the joined output of a streamed keys response:

{"props":{"name":"foo","n_val":3,"allow_mult":false,"precommit":[],"postcommit":[],"chash_keyfun":{"mod":"riak_core_util","fun":"chash_std_keyfun"},"linkfun":{"mod":"riak_kv_wm_link_walker","fun":"mapreduce_linkfun"},"old_vclock":86400,"young_vclock":20,"big_vclock":50,"small_vclock":10}}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}

If your client library supports per-chunk processing, each of those {"keys":[]} objects will be an encoded chunk.  The Ruby client and most of the other clients support this.

Sean Cribbs <sean at basho.com>
Developer Advocate
Basho Technologies, Inc.
http://basho.com/

On May 3, 2010, at 9:28 PM, Adam Hunter wrote:

> Hi All,
> 
> I apologize if this has been covered already.
> 
> In the wiki it says "If keys=stream, the response will be transferred using chunked-encoding, where each chunk is a JSON object" (on http://wiki.basho.com/display/RIAK/REST+API)
> 
> This doesn't seem to be the case, sometimes a json object is broken into several chunks.  Is this behavior correct?
> 
> Thanks,
> 
> Adam
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20100504/91ba002f/attachment.html>


More information about the riak-users mailing list