[GitHub] [phoenix] kadirozde opened a new pull request #621: PHOENIX-5562 The last concurrent update can complete the last write p…

[GitBox <gi...@apache.org>]

kadirozde opened a new pull request #621: PHOENIX-5562 The last concurrent update can complete the last write p…
URL: https://github.com/apache/phoenix/pull/621
 
 
   …hase
   In the current implementation, we have two pending-rows sets. The first one is at the table region level and the second one is at the batch level. The table region level set is a set of structures, one for each active row. This per row structure includes the row key, the timestamp of the last update on the row, and the number of concurrent updates on the row (i.e., the reference count). The second set is a simply set of row keys such that the corresponding rows for these row keys have at least one pending update at the time this batch is in the first phase. It turns out that we do not actually need the batch level set. All we need is that after acquiring the lock for the second time for a given update, we need to check if the update is the last update for the row using the region level set. if so, the last phase is executed. Otherwise, it is skipped.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services