Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-18842

The hbase shell clone_snaphost command returns bad error message

    XMLWordPrintableJSON

Details

    • Hide
      <!-- markdown -->

      When attempting to clone a snapshot but using a namespace that does not exist, the HBase shell will now correctly report the exception as caused by the passed namespace. Previously, the shell would report that the problem was an unknown namespace but it would claim the user provided table name was not found as a namespace. Both before and after this change the shell properly used the passed namespace to attempt to handle the request.
      Show
      <!-- markdown --> When attempting to clone a snapshot but using a namespace that does not exist, the HBase shell will now correctly report the exception as caused by the passed namespace. Previously, the shell would report that the problem was an unknown namespace but it would claim the user provided table name was not found as a namespace. Both before and after this change the shell properly used the passed namespace to attempt to handle the request.

    Description

      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:

      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'

      It should rather say:

      ERROR: Unknown namespace someNamespaceName!

      Attachments

        Activity

          People

            ThorGutierrez Thoralf Gutierrez
            ThorGutierrez Thoralf Gutierrez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: