[
https://issues.apache.org/jira/browse/HBASE-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198102#comment-16198102
]
Hudson commented on HBASE-18842:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3859 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3859/])
HBASE-18842 Fix unknown namespace message in clone_snapshot (jyates: rev
0ff4f5fba9cef8b4dea599357d935b47f6151152)
* (edit) hbase-shell/src/main/ruby/shell/commands/clone_snapshot.rb
* (edit) hbase-shell/src/test/ruby/shell/commands_test.rb
> 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, 3.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
(v6.4.14#64029)