[
https://issues.apache.org/jira/browse/OMID-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770384#comment-16770384
]
Yonatan Gottesman commented on OMID-131:
----------------------------------------
Hi [~lhofhansl], this is what we talked about.
If i understood you correctly you prefer the option in which we store the
families and not rows. This way there will be shadow cells for each family and
a region wont have to query another region for it. But it wont be good if your
transactions have many families (for example family for each cell). am i
correct?
([~ohads])
> Enhance row level conlict detection to reduce client memory footprint.
> ----------------------------------------------------------------------
>
> Key: OMID-131
> URL: https://issues.apache.org/jira/browse/OMID-131
> Project: Apache Omid
> Issue Type: Improvement
> Reporter: Yonatan Gottesman
> Assignee: Yonatan Gottesman
> Priority: Major
>
> Currently even if omid is working in row level conflict detection, all the
> cells are kept by the client until after commit for writing shadow cells or
> removing them after abort.
> Instead the client should store only the rows or only the family.
> If we choose to store only the row, the client memory footprint will be
> smaller, but if a region server wants to query a shadow cell for a cell it
> might have to query a different region.
> On the other hand client can store the famelies of a writeset. This will have
> a bigger footprint if we have lots of families but if a region queries a
> shadow cell it will be on the same region.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
