Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id AFA5D200D1F for ; Fri, 13 Oct 2017 23:50:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id ADEEB1609E9; Fri, 13 Oct 2017 21:50:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id F3B611609CA for ; Fri, 13 Oct 2017 23:50:05 +0200 (CEST) Received: (qmail 58044 invoked by uid 500); 13 Oct 2017 21:50:05 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 58033 invoked by uid 99); 13 Oct 2017 21:50:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Oct 2017 21:50:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 602221A23E0 for ; Fri, 13 Oct 2017 21:50:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id TbsYbXSxJe7o for ; Fri, 13 Oct 2017 21:50:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 08CF85F3E3 for ; Fri, 13 Oct 2017 21:50:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 77424E0E80 for ; Fri, 13 Oct 2017 21:50:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3E61124390 for ; Fri, 13 Oct 2017 21:50:00 +0000 (UTC) Date: Fri, 13 Oct 2017 21:50:00 +0000 (UTC) From: "Chia-Ping Tsai (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-18966) Use non-sync TimeRangeTracker as a replacement for TimeRange in ImmutableSegment MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 13 Oct 2017 21:50:06 -0000 [ https://issues.apache.org/jira/browse/HBASE-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18966: ----------------------------------- Status: Patch Available (was: Open) > Use non-sync TimeRangeTracker as a replacement for TimeRange in ImmutableSegment > -------------------------------------------------------------------------------- > > 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, HBASE-18966.v3.patch > > > The in-memory compaction/merge updates only the {{TimeRangeTracker}} when creating new {{ImmutableSegment}}, but the time information used to do time filter is the {{TimeRange}} rather than {{TimeRangeTracker}}. 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. > The {{TimeRange}} was used to be a snapshot of {{TimeRangeTracker}} for avoiding the sync operation happening in {{TimeRangeTracker}}. We can use non-sync trt introduced by HBASE-18753 to replace the {{TimeRange}}. -- This message was sent by Atlassian JIRA (v6.4.14#64029)