You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/03/12 23:41:34 UTC

[jira] [Commented] (HBASE-15447) Improve javadocs description for Delete methods

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

stack commented on HBASE-15447:
-------------------------------

Makes sense. Throw up a patch if you have a moment [~wchevreuil]


> Improve javadocs description for Delete methods
> -----------------------------------------------
>
>                 Key: HBASE-15447
>                 URL: https://issues.apache.org/jira/browse/HBASE-15447
>             Project: HBase
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Wellington Chevreuil
>            Assignee: Wellington Chevreuil
>            Priority: Minor
>
> Current javadoc for Delete operation is a bit confusing. Even though initial section does describe the proper behaviour, where calling delete without specifying timestamp will only delete records from now to the past, this is not as clear in the method specific description
> {noformat}
> public Delete(byte[] row)
> Create a Delete operation for the specified row.
> If no further operations are done, this will delete everything associated with the specified row (all versions of all columns in all families).
> Parameters:
> row - row key
> {noformat}
> The description can lead to the conclusion that all versions will be deleted. But that's not true if a row has a future timestamp. Although this is a very unusual scenario (having a future timestamp), it should still be clarified.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)