asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Jacobs (Code Review)" <do-not-re...@asterixdb.incubator.apache.org>
Subject Change in asterixdb[master]: Disable search in upsert with no secondary indexes
Date Mon, 08 May 2017 16:59:55 GMT
Steven Jacobs has posted comments on this change.

Change subject: Disable search in upsert with no secondary indexes
......................................................................


Patch Set 1:

Hey Abdullah,
I wanted to ask about this change because it actually might help with some experiments that
I'm running. I'm confused about how you can upsert without doing any search. Does this mean
that the old record will still be there but left on an older component and so not read, and
the new version will always be put on the newest component? Does this mean that many upsets
of the same keys would lead to lots of unneeded data in the older components?

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/1711
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I4af1dc73ec909b98ce0c981c687f1b9bf13030fa
Gerrit-PatchSet: 1
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: abdullah alamoudi <bamousaa@gmail.com>
Gerrit-Reviewer: Ildar Absalyamov <ildar.absalyamov@gmail.com>
Gerrit-Reviewer: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Gerrit-Reviewer: Steven Jacobs <sjaco002@ucr.edu>
Gerrit-Reviewer: Yingyi Bu <buyingyi@gmail.com>
Gerrit-HasComments: No

Mime
View raw message