Out of the box, Phoenix will provide the same semantics that HBase does
for concurrent updates to a (data) table.
https://hbase.apache.org/acid-semantics.html
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?
