You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jesse Yates (JIRA)" <ji...@apache.org> on 2017/09/18 22:40:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16170850#comment-16170850 ]
Jesse Yates commented on HBASE-18842:
-------------------------------------
Any chance for a patch [~ThorGutierrez]? Looks like we could do a light hack where commands could optionally handle exceptions to generate custom ruby exceptions.
> 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
> Priority: Minor
>
> 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)