From issues-return-328946-archive-asf-public=cust-asf.ponee.io@hbase.apache.org Wed Jan 10 13:59:05 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 5A33718072F for ; Wed, 10 Jan 2018 13:59:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 49E36160C40; Wed, 10 Jan 2018 12:59:05 +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 8D03E160C23 for ; Wed, 10 Jan 2018 13:59:04 +0100 (CET) Received: (qmail 3018 invoked by uid 500); 10 Jan 2018 12:59:03 -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 3007 invoked by uid 99); 10 Jan 2018 12:59:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jan 2018 12:59:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 38E19180782 for ; Wed, 10 Jan 2018 12:59:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -107.911 X-Spam-Level: X-Spam-Status: No, score=-107.911 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id fG89MapQEO8c for ; Wed, 10 Jan 2018 12:59:02 +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 6C26E5F39D for ; Wed, 10 Jan 2018 12:59:02 +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 B7F1DE0EEF for ; Wed, 10 Jan 2018 12:59:00 +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 70331274C8 for ; Wed, 10 Jan 2018 12:59:00 +0000 (UTC) Date: Wed, 10 Jan 2018 12:59:00 +0000 (UTC) From: "Chia-Ping Tsai (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-19740) Repeated error message for NamespaceExistException MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-19740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320191#comment-16320191 ] Chia-Ping Tsai commented on HBASE-19740: ---------------------------------------- Please remove the extra description from NamespaceExistException for v2 patch. {code} public NamespaceExistException(String namespace) { super("Namespace " + namespace + " already exists"); } {code} > Repeated error message for NamespaceExistException > -------------------------------------------------- > > Key: HBASE-19740 > URL: https://issues.apache.org/jira/browse/HBASE-19740 > Project: HBase > Issue Type: Bug > Reporter: Ted Yu > Assignee: Ted Yu > Priority: Minor > Attachments: 19740.v2.txt > > > The following can be observed in TestAsyncNamespaceAdminApi test output: > {code} > 2018-01-09 07:55:08,685 INFO [Default-IPC-NioEventLoopGroup-5-2] client.RawAsyncHBaseAdmin$NamespaceProcedureBiConsumer(2374): Operation: CREATE_NAMESPACE, Namespace: TestNamespacens1 failed with Namespace Namespace TestNamespacens1 already exists already exists > {code} > This was due to ForeignExceptionUtil.toIOException() recreating NamespaceExistException, resulting in "already exists" appended one more time. -- This message was sent by Atlassian JIRA (v6.4.14#64029)