You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/04/05 20:03:00 UTC

[jira] [Updated] (HBASE-18842) The hbase shell clone_snaphost command returns bad error message

     [ https://issues.apache.org/jira/browse/HBASE-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-18842:
--------------------------
    Fix Version/s:     (was: 3.0.0)

> The hbase shell clone_snaphost command returns bad error message
> ----------------------------------------------------------------
>
>                 Key: HBASE-18842
>                 URL: https://issues.apache.org/jira/browse/HBASE-18842
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Thoralf Gutierrez
>            Assignee: Jesse Yates
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: 0001-HBASE-18842-Fix-unknown-namespace-message-in-clone_s.patch, 0002-HBASE-18842-Fix-unknown-namespace-message-in-clone_s.patch, 0003-HBASE-18842-Fix-unknown-namespace-message-in-clone_s.patch, 0004-HBASE-18842-Fix-unknown-namespace-message-in-clone_s.patch, 0005-HBASE-18842-Fix-unknown-namespace-message-in-clone_s.patch
>
>
> When you call the hbase shell clone_snapshot command with a target namespace that doesn't exist, you get an error message, but the variable used to identify the inexistent namespace is wrong:
> {noformat}
> hbase(main):001:0> clone_snapshot 'someSnapshotName', 'someNamespaceName:someTableName'
> ERROR: Unknown namespace someSnapshotName!
> Create a new table by cloning the snapshot content.
> There're no copies of data involved.
> And writing on the newly created table will not influence the snapshot data.
> Examples:
>   hbase> clone_snapshot 'snapshotName', 'tableName'
>   hbase> clone_snapshot 'snapshotName', 'namespace:tableName'
> {noformat}
> It should rather say:
> {noformat}
> ERROR: Unknown namespace someNamespaceName!
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)