hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18966) In-memory compaction/merge should update its time range
Date Fri, 13 Oct 2017 09:26:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203286#comment-16203286
] 

Anoop Sam John commented on HBASE-18966:
----------------------------------------

This patch uses the SYNC or NON_SYNC version of the TRT correctly now. But we dont need any
change to update the TRT (TR) when the in memory flush/compaction is happening? This is for
the EAGER type where we may drop some of the Cells.  In other types, we will just retain all
Cells.  Sorry I could not see any related code. Or is it like that is already happening? If
so pls change the jira subject/desc accordingly.

> In-memory compaction/merge should update its time range
> -------------------------------------------------------
>
>                 Key: HBASE-18966
>                 URL: https://issues.apache.org/jira/browse/HBASE-18966
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>             Fix For: 2.0.0-beta-1
>
>         Attachments: HBASE-18966.v0.patch, HBASE-18966.v1.patch, HBASE-18966.v2.patch,
HBASE-18966.v2.patch
>
>
> The in-memory compaction/merge do the great job of optimizing the memory layout for cells,
but they don't update its {{TimeRange}}. It don't cause any bugs currently because the {{TimeRange}}
is used for store-level ts filter only and the default {{TimeRange}} of {{ImmutableSegment}}
created by in-memory compaction/merge has the maximum ts range.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message