Re: last_write_wins

2014-01-30 Thread Edgar Veiga
Also, Using last_write_wins = true, do I need to always send the vclock while on a PUT request? In the official documention it says that riak will look only at the timestamp of the requests. Best regards, On 29 January 2014 10:29, Edgar Veiga edgarmve...@gmail.com wrote: Hi Russel

Re: last_write_wins

2014-01-30 Thread Russell Brown
On 30 Jan 2014, at 10:37, Edgar Veiga edgarmve...@gmail.com wrote: Also, Using last_write_wins = true, do I need to always send the vclock while on a PUT request? In the official documention it says that riak will look only at the timestamp of the requests. Ok, from what you’ve said

Re: last_write_wins

2014-01-30 Thread Russell Brown
On 30 Jan 2014, at 10:58, Guido Medina guido.med...@temetra.com wrote: Hi, Now I'm curious too, according to http://docs.basho.com/riak/latest/ops/advanced/configs/configuration-files/ the default value for Erlang property last_write_wins is false, now, if 95% of the buckets/keys have

Re: last_write_wins

2014-01-30 Thread Guido Medina
Jan 2014, at 10:58, Guido Medina guido.med...@temetra.com mailto:guido.med...@temetra.com wrote: Hi, Now I'm curious too, according to http://docs.basho.com/riak/latest/ops/advanced/configs/configuration-files/ the default value for Erlang property last_write_wins is false, now, if 95

Re: last_write_wins

2014-01-30 Thread Edgar Veiga
, Russell Brown russell.br...@me.com wrote: On 30 Jan 2014, at 10:37, Edgar Veiga edgarmve...@gmail.com wrote: Also, Using last_write_wins = true, do I need to always send the vclock while on a PUT request? In the official documention it says that riak will look only at the timestamp

Re: last_write_wins

2014-01-30 Thread Jason Campbell
, but there is other software that will work much better. I hope this helps, Jason Campbell - Original Message - From: Edgar Veiga edgarmve...@gmail.com To: Russell Brown russell.br...@me.com Cc: riak-users riak-users@lists.basho.com Sent: Friday, 31 January, 2014 3:20:42 AM Subject: Re: last_write_wins

Re: last_write_wins

2014-01-30 Thread Eric Redmond
: riak-users riak-users@lists.basho.com Sent: Friday, 31 January, 2014 3:20:42 AM Subject: Re: last_write_wins I'll try to explain this the best I can, although it's a simples architecture I'm not describing it in my native language :) I have a set of node.js workers (64 for now

Re: last_write_wins

2014-01-30 Thread Edgar Veiga
Sent: Friday, 31 January, 2014 3:20:42 AM Subject: Re: last_write_wins I'll try to explain this the best I can, although it's a simples architecture I'm not describing it in my native language :) I have a set of node.js workers (64 for now) that serve as a cache/middleware layer for a dozen

Re: last_write_wins

2014-01-30 Thread Eric Redmond
: Re: last_write_wins I'll try to explain this the best I can, although it's a simples architecture I'm not describing it in my native language :) I have a set of node.js workers (64 for now) that serve as a cache/middleware layer for a dozen of php applications. Each worker deals

Re: last_write_wins

2014-01-30 Thread Edgar Veiga
@lists.basho.com Sent: Friday, 31 January, 2014 3:20:42 AM Subject: Re: last_write_wins I'll try to explain this the best I can, although it's a simples architecture I'm not describing it in my native language :) I have a set of node.js workers (64 for now) that serve as a cache/middleware layer

Re: last_write_wins

2014-01-30 Thread Edgar Veiga
software that will work much better. I hope this helps, Jason Campbell - Original Message - From: Edgar Veiga edgarmve...@gmail.com To: Russell Brown russell.br...@me.com Cc: riak-users riak-users@lists.basho.com Sent: Friday, 31 January, 2014 3:20:42 AM Subject: Re: last_write_wins

Re: last_write_wins

2014-01-30 Thread Edgar Veiga
...@basho.com Cc: Jason Campbell xia...@xiaclo.net, riak-users riak-users@lists.basho.com, Russell Brown russell.br...@me.com Sent: Friday, 31 January, 2014 9:54:33 AM Subject: Re: last_write_wins Hi! I think that you are making some kind of confusion here... I'm not using riak for cache purposes

Re: last_write_wins

2014-01-30 Thread John Daily
, and separately we have the a last_write_wins configuration parameter, and they’re not the same thing. I’m going to stick to last_write_wins to be explicit when I’m referring to the parameter, and “last write wins” when referring to the strategy. (Informally I often refer to LWW as the strategy and lww

Re: last_write_wins

2014-01-29 Thread Edgar Veiga
tl;dr If I guarantee that the same key is only written with a 5 second interval, is last_write_wins=true profitable? On 27 January 2014 23:25, Edgar Veiga edgarmve...@gmail.com wrote: Hi there everyone! I would like to know, if my current application is a good use case to set

Re: last_write_wins

2014-01-29 Thread Russell Brown
On 29 Jan 2014, at 09:57, Edgar Veiga edgarmve...@gmail.com wrote: tl;dr If I guarantee that the same key is only written with a 5 second interval, is last_write_wins=true profitable? It depends. Does the value you write depend in anyway on the value you read, or is it always that you

Re: last_write_wins

2014-01-29 Thread Edgar Veiga
, is last_write_wins=true profitable? It depends. Does the value you write depend in anyway on the value you read, or is it always that you are just getting a totally new value that replaces what is in Riak (regardless what is in Riak)? On 27 January 2014 23:25, Edgar Veiga edgarmve

last_write_wins

2014-01-27 Thread Edgar Veiga
Hi there everyone! I would like to know, if my current application is a good use case to set last_write_wins to true. Basically I have a cluster of node.js workers reading and writing to riak. Each node.js worker is responsible for a set of keys, so I can guarantee some kind of non distributed