[
https://issues.apache.org/jira/browse/HADOOP-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Duxbury updated HADOOP-1550:
----------------------------------
Attachment: 1550-v5.patch
OK, fixed the javadoc issues and lengthy lines.
The null check in assertCellValuePresent is necessary because if the result is
null, attempting to create a string out of it throws an exception instead of a
nice assertion failure.
And yes, I did in fact find a bug in getFull. It would only check if the cell
was deleted in the HStore, not the memcache. This bug was introduced by me some
time ago when I "fixed" getFull to not return deleted values. Now it's *really*
fixed.
> [hbase] No means of deleting a'row' nor all members of a column family
> ----------------------------------------------------------------------
>
> Key: HADOOP-1550
> URL: https://issues.apache.org/jira/browse/HADOOP-1550
> Project: Hadoop
> Issue Type: Improvement
> Components: contrib/hbase
> Reporter: stack
> Assignee: Bryan Duxbury
> Attachments: 1550-v2.patch, 1550-v3.patch, 1550-v4.patch,
> 1550-v5.patch, 1550.patch
>
>
> There is no support in hbase currently for deleting a row -- i.e. remove all
> columns and their versions keyed by a particular row id. Nor is there a
> means of passing in a row id and column family name having hbase delete all
> members of the column family (for the designated row).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
