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 8F0F7200CD6 for ; Mon, 31 Jul 2017 23:31:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8DAEE165E31; Mon, 31 Jul 2017 21:31:07 +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 D741E165E52 for ; Mon, 31 Jul 2017 23:31:06 +0200 (CEST) Received: (qmail 15098 invoked by uid 500); 31 Jul 2017 21:31:04 -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 14826 invoked by uid 99); 31 Jul 2017 21:31:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Jul 2017 21:31:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 019B2C4761 for ; Mon, 31 Jul 2017 21:31:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.001 X-Spam-Level: X-Spam-Status: No, score=-100.001 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_BLOCKED=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id hCGIXMzU4H5A for ; Mon, 31 Jul 2017 21:31:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 063855F572 for ; Mon, 31 Jul 2017 21:31: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 48493E0E65 for ; Mon, 31 Jul 2017 21:31:02 +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 5265F24DC7 for ; Mon, 31 Jul 2017 21:31:01 +0000 (UTC) Date: Mon, 31 Jul 2017 21:31:01 +0000 (UTC) From: "Enis Soztutar (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HBASE-18080) [C++] Use millisecond for various timeout settings MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 31 Jul 2017 21:31:07 -0000 [ https://issues.apache.org/jira/browse/HBASE-18080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar resolved HBASE-18080. ----------------------------------- Resolution: Won't Fix > [C++] Use millisecond for various timeout settings > -------------------------------------------------- > > Key: HBASE-18080 > URL: https://issues.apache.org/jira/browse/HBASE-18080 > Project: HBase > Issue Type: Sub-task > Reporter: Xiaobing Zhou > Assignee: Xiaobing Zhou > > In configuration, millisecond is the default unit, however, many places are using nanosecond, frequent milli-to-nano conversions are making code verbose. -- This message was sent by Atlassian JIRA (v6.4.14#64029)