[
https://issues.apache.org/jira/browse/HBASE-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thoralf Gutierrez updated HBASE-18842:
--------------------------------------
Attachment: 0002-HBASE-18842-Fix-unknown-namespace-message-in-clone_s.patch
This second version complies a bit more with rubocop and ruby-lint.
To be more explicit about the tests performed:
I have built the `branch-1.4` branch locally with my change, and tested the
`clone_snapshot` command on an unknown namespace on an HBase 1.4 cluster. The
error give the expected message:
{noformat}
hbase(main):001:0> clone_snapshot 'tmp_snap', 'bad_namespace:some_table'
ERROR: Unknown namespace 'bad_namespace'!
{noformat}
> 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
> Attachments:
> 0001-HBASE-18842-Fix-unknown-namespace-message-in-clone_s.patch,
> 0002-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
(v6.4.14#64029)
