hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7353) [shell] have list and list_snapshot return jruby string arrays.
Date Fri, 14 Dec 2012 01:44:13 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531903#comment-13531903

Hadoop QA commented on HBASE-7353:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3539//console

This message is automatically generated.
> [shell] have list and list_snapshot return jruby string arrays.
> ---------------------------------------------------------------
>                 Key: HBASE-7353
>                 URL: https://issues.apache.org/jira/browse/HBASE-7353
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client, shell
>    Affects Versions: hbase-6055
>            Reporter: Jonathan Hsieh
>         Attachments: hbase-7353.patch
> It is really convenient to allow comamnds like list and list_snapshots return a jruby
array of values in the hbase shell.
> it allows for nice things like this:
> {code}
> # drop all tables starting with foo
> list("foo.*").map { |t| disable t; drop t }
> {code}
> or 
> {code}
> # clone all tables that start with bar
> list_snapshots("bar.*").map { |s| clone_snapshot s, s + "-table"}
> {code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message