Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <12369651.1184208667938.JavaMail.jira@brutus>
Date: Wed, 11 Jul 2007 19:51:07 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1574) [hbase] Concurrent creates of a
 table named 'X' all succeed
In-Reply-To: <11515177.1183771384494.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511948 ] 

stack commented on HADOOP-1574:
-------------------------------

No.  This test was catching RemoteException and undoing it to pull out TableExistsException. The new patch changes the test to instead catch TableExistsException, which should still hold after you do your new commit (Thanks for asking)

> [hbase] Concurrent creates of a table named 'X' all succeed
> -----------------------------------------------------------
>
>                 Key: HADOOP-1574
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1574
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/hbase
>            Reporter: stack
>            Assignee: stack
>            Priority: Minor
>         Attachments: duptable-v2.patch, duptable-v3.patch, duptable.patch, hadoop-1574-v4.patch, hadoop-1574-v5.patch
>
>
> If multiple threads all try to create a table of a particular, all succeed.  It makes for a mess. 
> Create table needs to be synchronized so only one thread creates a table and subsequent threads fail with 'table already exits'.  The test for pre-existence also needs fixing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.