[jira] [Reopened] (HBASE-8231) delete tests in table_tests.rb(TestShell) always running on empty table.

["Ted Yu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Yu reopened HBASE-8231:
---------------------------

    
> delete tests in table_tests.rb(TestShell) always running on empty table.
> ------------------------------------------------------------------------
>
>                 Key: HBASE-8231
>                 URL: https://issues.apache.org/jira/browse/HBASE-8231
>             Project: HBase
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.95.0, 0.94.6
>            Reporter: rajeshbabu
>            Assignee: rajeshbabu
>             Fix For: 0.95.1, 0.94.7
>
>         Attachments: HBASE-8231.patch
>
>
> In ruby,tests within the same test class are invoked in alphabetical order,so delete test cases are running on a table before adding any entry.
> TestShell logs showing "Row not found" for each delete test everytime.
> {code}
> ERROR: Row Not Found
> Here is some help for this command:
> Delete all cells in a given row; pass a table name, row, and optionally
> a column and timestamp. Examples:
>   hbase> deleteall 't1', 'r1'
>   hbase> deleteall 't1', 'r1', 'c1'
>   hbase> deleteall 't1', 'r1', 'c1', ts1
> The same commands also can be run on a table reference. Suppose you had a reference
> t to table 't1', the corresponding command would be:
>   hbase> t.deleteall 'r1'
>   hbase> t.deleteall 'r1', 'c1'
>   hbase> t.deleteall 'r1', 'c1', ts1
> {code}
> Before deleting a row we are checking whether the row is present or not.
> {code}
>     def _deleteall_internal(row, column = nil, timestamp = org.apache.hadoop.hbase.HConstants::LATEST_TIMESTAMP)
>       raise ArgumentError, "Row Not Found" if _get_internal(row).nil?
> {code}
> Need to improve delete tests in table_tests.rb.

--
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