[
https://issues.apache.org/jira/browse/HBASE-18752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194177#comment-16194177
]
Anoop Sam John commented on HBASE-18752:
----------------------------------------
Thanks.. Am generally +1 on this. Still would be nice to run PE random write
tests for a bit longer duration of say 10 mns to see the impact of the overhead
in flush.
Also in COmpacting MemStore when Policy is EAGER, for each of the
ImmutableSegment creation, we will recalculate this TR? There also dropping of
dup cells etc happens. Pls double check once. May be a test case also for that
would be nice to have.
> Recalculate the TimeRange in flushing snapshot to store file
> ------------------------------------------------------------
>
> Key: HBASE-18752
> URL: https://issues.apache.org/jira/browse/HBASE-18752
> Project: HBase
> Issue Type: Sub-task
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-18752.v0.patch, HBASE-18752.v1.patch
>
>
> We drop superfluous cells in flushing, hence the TimeRange from snapshot is
> inaccurate for the storefile. We should recalculate the TimeRange for the
> storefile, but the side-effect is the extra cost - we need to extract the
> timestamp from cell (ByteBufferCell).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
