You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/06/16 21:13:45 UTC

[jira] Created: (HBASE-692) Two tables of same name if first with column family A, B, C and second with column family D

Two tables of same name if first with column family A, B, C and second with column family D
-------------------------------------------------------------------------------------------

                 Key: HBASE-692
                 URL: https://issues.apache.org/jira/browse/HBASE-692
             Project: Hadoop HBase
          Issue Type: Bug
            Reporter: stack
             Fix For: 0.2.0


I see two tables of same name in an hbase instance.  The first was made with column familes 1, 2, 3.  I then dropped that table and made a new one with column family 4.  I notice now -- or rather Jim Firby noticed --  that two tables are showing in the UI, both named the same; one with familes 1, 2, and 3 with the other showing column family 4.

Scanning etc., seems to work properly.  Looking on disk, I see one subdir named for the table with all column families under it.

Haven't tried to reproduce.

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


[jira] Resolved: (HBASE-692) Two tables of same name if first with column family A, B, C and second with column family D

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-692.
-------------------------

    Resolution: Cannot Reproduce

Cannot reproduce on trunk.  Closing.

> Two tables of same name if first with column family A, B, C and second with column family D
> -------------------------------------------------------------------------------------------
>
>                 Key: HBASE-692
>                 URL: https://issues.apache.org/jira/browse/HBASE-692
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>             Fix For: 0.2.0
>
>
> I see two tables of same name in an hbase instance.  The first was made with column familes 1, 2, 3.  I then dropped that table and made a new one with column family 4.  I notice now -- or rather Jim Firby noticed --  that two tables are showing in the UI, both named the same; one with familes 1, 2, and 3 with the other showing column family 4.
> Scanning etc., seems to work properly.  Looking on disk, I see one subdir named for the table with all column families under it.
> Haven't tried to reproduce.

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


[jira] Commented: (HBASE-692) Two tables of same name if first with column family A, B, C and second with column family D

Posted by "stack (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606152#action_12606152 ] 

stack commented on HBASE-692:
-----------------------------

Issue was seen on branch.

> Two tables of same name if first with column family A, B, C and second with column family D
> -------------------------------------------------------------------------------------------
>
>                 Key: HBASE-692
>                 URL: https://issues.apache.org/jira/browse/HBASE-692
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>             Fix For: 0.2.0
>
>
> I see two tables of same name in an hbase instance.  The first was made with column familes 1, 2, 3.  I then dropped that table and made a new one with column family 4.  I notice now -- or rather Jim Firby noticed --  that two tables are showing in the UI, both named the same; one with familes 1, 2, and 3 with the other showing column family 4.
> Scanning etc., seems to work properly.  Looking on disk, I see one subdir named for the table with all column families under it.
> Haven't tried to reproduce.

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