[
https://issues.apache.org/jira/browse/OMID-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810154#comment-16810154
]
Lars Hofhansl edited comment on OMID-142 at 4/4/19 10:27 PM:
-------------------------------------------------------------
Cool.
The low watermark would move up very slowly then, and only if there's
transaction activity, and hence old garbage would be cleaned out for a while.
But that's a minor problem.
Edit: I see the size of the CommitHashMap is hardcoded to 1000. Isn't that
pretty arbitrary?
I.e. why not 100 or 1000000?
Should it rather be bounded by time? (hmm... I guess perhaps not when we're not
using WORLD_TIME)
was (Author: lhofhansl):
Cool.
The low watermark would move up very slowly then, and only if there's
transaction activity, and hence old garbage would be cleaned out for a while.
But that's a minor problem.
> Omid GC fails in Phoenix does not remove all data
> -------------------------------------------------
>
> Key: OMID-142
> URL: https://issues.apache.org/jira/browse/OMID-142
> Project: Apache Omid
> Issue Type: Bug
> Affects Versions: 1.0.1
> Reporter: Lars Hofhansl
> Assignee: Yonatan Gottesman
> Priority: Major
> Attachments: 142-test.txt, omid142.patch
>
>
> When you insert a bunch of data into a table, followed by a DELETE FROM
> <table>, then flush and compact the table in HBase, the data is not removed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
