4年12月10日 22:42
收件人: user@cassandra.apache.org
主题: Re: UPDATE statement is failed
Writing then immediately reading the same data (or reading then immediately
writing) are both antipatterns in any eventually consistent system, Cassandra
included.
You may need to investigate Compare and Set operat
rrectly.
>
>
>
> Peter
>
> *发件人:* 鄢来琼 [mailto:laiqiong@gtafe.com]
> *发送时间:* 2014年12月3日 13:08
> *收件人:* user@cassandra.apache.org
> *主题:* re: UPDATE statement is failed
>
>
>
> The system setting is as the following:
>
>
>
> Cluster replication:
>
&g
[mailto:laiqiong@gtafe.com]
发送时间: 2014年12月3日 13:08
收件人: user@cassandra.apache.org
主题: re: UPDATE statement is failed
The system setting is as the following:
Cluster replication:
replication = {'class': 'NetworkTopologyStrategy', 'GTA_SZ_DC1':2}
Totally, 5 Nodes,
OS o
TA Information Technology Co., Ltd.
=
Mobile: 18620306659
E-Mail: laiqiong@gtafe.com
Website: http://www.gtafe.com/
=
发件人: 鄢来琼 [mailto:laiqiong@gtafe.com]
发送时间: 2014年12月3日 11:49
收件人: user@cassandra.apache.org
主题: UPDATE statem
Hi ALL,
There is a grogram to consume messages from queue; according to the message,
the program will READ a row and then UPDATE the row;
BUT, sometimes, the UPDATE statement is fail, the result of READ statement is
also the old content before UDPATE.
Any suggestions from you are appreciated.
Th
