> Jonathan that is correct - it is just a result of the chunked encoding.
> >
> > --gordon
> >
> > On Oct 20, 2011, at 11:02 , Jonathan Langevin wrote:
> >
> > If I run a curl request to pull back a list of keys, streamed, the output
> > has multiple empt
t 20, 2011, at 11:02 , Jonathan Langevin wrote:
>>
>> If I run a curl request to pull back a list of keys, streamed, the output
>> has multiple empty arrays, like so:
>>
>> $ curl -i http://localhost:8098/buckets/User/keys?keys=stream
>> HTTP/1.1 200 OK
>> Va
that is correct - it is just a result of the chunked encoding.
>
> --gordon
>
> On Oct 20, 2011, at 11:02 , Jonathan Langevin wrote:
>
> If I run a curl request to pull back a list of keys, streamed, the output
> has multiple empty arrays, like so:
>
> $ curl -i http://l
If I run a curl request to pull back a list of keys, streamed, the output
has multiple empty arrays, like so:
$ curl -i http://localhost:8098/buckets/User/keys?keys=stream
HTTP/1.1 200 OK
Vary: Accept-Encoding
Transfer-Encoding: chunked
Server: MochiWeb/1.1 WebMachine/1.9.0 (participate in the
quot;keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{&quo
;
>>>>>>>>
>>>>>>>> On May 4, 2010, at 9:22 AM, Sean Cribbs wrote:
>>>>>>>>
>>>>>>>>> This behavior is unchanged since its implementation in 0.8 or 0.9.
>>>>>>>>&g
ys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}
If your client library supports per-ch
means, here's the joined output
>>>>>>>> of a streamed keys response:
>>>>>>>>
>>>>>>>> {"props":{"name":"foo","n_val":3,"allow_mult":false,"precommit":[],"
t;>>> {"props":{"name":"foo","n_val":3,"allow_mult":false,"precommit":[],"postcommit":[],"chash_keyfun":{"mod":"riak_core_util","fun":"chash_std_keyfun"},"li
mit":[],"postcommit":[],"chash_keyfun":{"mod":"riak_core_util","fun":"chash_std_keyfun"},"linkfun":{"mod":"riak_kv_wm_link_walker","fun":"mapreduce_linkfun"},"old_vclock":86400,"
eys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys&qu
t;:86400,"young_vclock":20,"big_vclock":50,"small_vclock":10}}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{&qu
":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}
>>>
>>> If your client library supports per-chunk processing
uot;:[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}
>>
>> If your client library supports per-chunk processing, each of thos
]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}
>
> If your client library supports per-chunk
t;keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}{"keys":[]}
If your client library support
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
17 matches
Mail list logo
