Ildar Absalyamov has posted comments on this change. Change subject: Introduced new storage format bit, which signifies if the tuple in BTree was updated in-place ......................................................................
Patch Set 2: @Till 1)We had some asynchronous discussions about it with Abdullah & Mike and Mike was on board with it. This week I wanted to shot a message to dev@ explaining details of the change and why we need it. So stay tuned :) So far I just wanted to prototype it as a separate change, thus pushed it as a review. In a nutshell, the reason for the change is the current quirkiness of the way we deal with antimatter records & records updated in-place in BTrees. The result is that the same chain of insert-delete-upsert events can lead to a different state of the components depending on when the flush happened. Encoding additional information (aka change bit) allows to resolve this ambiguity. 2) Valid point, I'll have to think what kind of tests would be suitable here (presumably unit tests) -- To view, visit https://asterix-gerrit.ics.uci.edu/1538 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: I12a67eff8431b52d1f9051b793a5a64b15c009e9 Gerrit-PatchSet: 2 Gerrit-Project: asterixdb Gerrit-Branch: master Gerrit-Owner: Ildar Absalyamov <ildar.absalya...@gmail.com> Gerrit-Reviewer: Ildar Absalyamov <ildar.absalya...@gmail.com> Gerrit-Reviewer: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Gerrit-Reviewer: Michael Blow <mb...@apache.org> Gerrit-Reviewer: Till Westmann <ti...@apache.org> Gerrit-HasComments: No
