hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19740) Repeated error message for NamespaceExistException
Date Wed, 10 Jan 2018 17:19:00 GMT

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

Josh Elser commented on HBASE-19740:

bq. The way to resolve this issue is that we should NOT revise the passed error message. No
one can remember the NamespaceExistException will add the extra description to the passed

Yeah, felt very brittle to me.

bq. We can use the significant error message when creating the NamespaceExistException.

Sounds like a better approach to me.

> 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

View raw message