phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <>
Subject Re: On duplicate key update
Date Mon, 26 Aug 2019 23:28:14 GMT
Out of the box, Phoenix will provide the same semantics that HBase does 
for concurrent updates to a (data) table.

If you're also asking about how index tables remain in sync, the answer 
is a bit more complicated (and has changed in recent versions).

On 8/26/19 2:51 PM, Jon Strayer wrote:
> How does atomic update work with multiple clients?  Assuming that there 
> is no matching record to begin with the access won’t be locked.  It 
> seems like two threads could write conflicting data since they both see 
> no existing record (NER).  Is that correct? Or is there something that 
> will serialize the writes so that only one of them sees the NER state?

View raw message