Are X-Riak-ClientId and RpbSetClientId deprecated?

Andres Jaan Tack andres.jaan.tack at eesti.ee
Sun Dec 18 13:32:20 EST 2011


Sean,

I understand that they are still used when provided. The more fundamental
question is: as good Riak citizens, should we consider Client IDs
deprecated, and stop using them in new projects?

--
Andres

2011/12/18 Sean Cribbs <sean at basho.com>

> Andres
>
> Client IDs are still used if the riak_kv / vnode_vclocks setting is false.
> If it is true, the client ID will simply be ignored. For compatibility's
> sake, it's best to send/set them still.
>
> On Sun, Dec 18, 2011 at 11:12 AM, Andres Jaan Tack <
> andres.jaan.tack at eesti.ee> wrote:
>
>> I guess the fundamental question is: In new clusters unaffected by
>> pre-1.0 shenanigans, should we *ever* be using client-provided ClientIds
>> in our vector clocks, or is this method deprecated?
>>
>> I ask because I was deep into figuring out how to do this efficiently
>> with the Riak PBC API for PUT requests, when I realized that the
>> documentation for HTTP PUT no longer even mentions it<http://wiki.basho.com/HTTP-Store-Object.html>
>> .
>>
>> If client-id isn't totally deprecated, I will probably start finding a
>> way to shoehorn it into individual PBC PUT requests, as keeping a
>> per-connection client id is very onwieldy. Please advise. :)
>>
>> --
>> Andres
>> _______________________________________________
>> riak-users mailing list
>> riak-users at lists.basho.com
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>
>>
>
>
> --
> Sean Cribbs <sean at basho.com>
> Developer Advocate
> Basho Technologies, Inc.
> http://www.basho.com/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20111218/955d6e6e/attachment.html>


More information about the riak-users mailing list