asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Young-Seok Kim <>
Subject Question about upsert operation
Date Thu, 14 Jan 2016 19:41:48 GMT
Can someone help me understanding the following part in the upsert design
document ( ?

   - The secondary Upsert operator perform the following tasks:

   1. If the existing secondary key equals to the new secondary key, it is
   a NO OP.
   2. If a different old secondary key exists, it deletes the existing
   secondary key-primary key pair from the secondary index.
   3. If a different new secondary key exists, it inserts the new secondary
   key-primary key pair from the secondary index.

How can the third case happen?

Was there another upsert transaction T1 (upserting record R1 but not
committed yet) when this transaction T2 reached the secondary index, for
instance? Is this possible?
I think this example is not valid due to the guarantee of the primary key
locking in the primary index. T1 must be holding a exclusive lock on the
primary key of R1, so when T2 reached the primary index and read the R1, it
must either be waiting the T1 is over to get a lock on R1 or see the new
record upserted by T1. Thus, when T2 reads from the secondary index, it
must see the value upserted by T2. This is the second case.

Again, how can the third case happen?


On Thu, Jan 14, 2016 at 9:37 AM, Jenkins (Code Review) <> wrote:

> Jenkins has posted comments on this change.
> Change subject: Add Support for Upsert Operation
> ......................................................................
> Patch Set 13: Verified-1
> Build Unstable
> :
> --
> To view, visit
> To unsubscribe, visit
> Gerrit-MessageType: comment
> Gerrit-Change-Id: I8999000331795a5949d621d2dd003903e057a521
> Gerrit-PatchSet: 13
> Gerrit-Project: asterixdb
> Gerrit-Branch: master
> Gerrit-Owner: abdullah alamoudi <>
> Gerrit-Reviewer: Jenkins <>
> Gerrit-Reviewer: Taewoo Kim <>
> Gerrit-Reviewer: Till Westmann <>
> Gerrit-Reviewer: Young-Seok Kim <>
> Gerrit-Reviewer: abdullah alamoudi <>
> Gerrit-HasComments: No

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message