[
https://issues.apache.org/jira/browse/HBASE-12321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179892#comment-14179892
]
Jan Lukavsky commented on HBASE-12321:
--------------------------------------
I can think of two solutions:
# in the RecordWriter let the user know he does something that is not supposed
to work, or
# in the RegionServer make the Delete to delete the same data as would a call
to {{HTable#delete}}
The second solution seems tricky, because it would require to know *when* was
created the Delete and also *when* was issued each Put to HBase, because, it is
possible to write data with different stamps then 'now'.
The solution in RecordWriter can include either incrementing a counter or
throwing an exception.
What would be a better solution? Or is there any third option?
> Delete#deleteColumn seems not to work with bulkload
> ---------------------------------------------------
>
> Key: HBASE-12321
> URL: https://issues.apache.org/jira/browse/HBASE-12321
> Project: HBase
> Issue Type: Bug
> Components: Deletes, HFile, mapreduce
> Affects Versions: 0.94.6
> Reporter: Jan Lukavsky
> Priority: Minor
>
> When using call to {{Delete#deleteColumn(byte[], byte[])}} to produce
> KeyValues that are subsequently written to HFileOutputFormat and bulk loaded
> into HBase, the Delete seems to be ignored. The reason for this is likely to
> be the missing (HConstants.LATEST_TIMESTAMP) timestamp in the KeyValue with
> type {{KeyValue.Type.Delete}}. I think the RegionServer than cannot delete
> the contents of the column due to mismatch in the timestamp.
> When using {{Delete#deleteColumns}} everything works fine, because of
> different type {{KeyValue.Type.DeleteColumn}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
