You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2014/06/09 13:27:02 UTC
[jira] [Updated] (HBASE-11310) Delete constructor accepting another
Delete should copy the attributes also
[ https://issues.apache.org/jira/browse/HBASE-11310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ramkrishna.s.vasudevan updated HBASE-11310:
-------------------------------------------
Description:
The constructor in Delete
{code}
public Delete(final Delete d) {
this.row = d.getRow();
this.ts = d.getTimeStamp();
this.familyMap.putAll(d.getFamilyCellMap());
this.durability = d.durability;
}
{code}
should copy the attributes also. Similar bug was raised for Put also. I remember because I found while debugging an MR issue. Now while checking another MR issue found for delete it has not been done.
was:
The constructor in Delete
{code}
public Delete(final Delete d) {
this.row = d.getRow();
this.ts = d.getTimeStamp();
this.familyMap.putAll(d.getFamilyCellMap());
this.durability = d.durability;
}
{code}
should copy the attributes also. Similar bug was raised for Put also. I remember because I found while debugging an MR issue. Now while checking another MR issue I found for delete it has not been done.
> Delete constructor accepting another Delete should copy the attributes also
> ---------------------------------------------------------------------------
>
> Key: HBASE-11310
> URL: https://issues.apache.org/jira/browse/HBASE-11310
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Affects Versions: 0.98.3
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Fix For: 0.99.0, 0.98.4
>
>
> The constructor in Delete
> {code}
> public Delete(final Delete d) {
> this.row = d.getRow();
> this.ts = d.getTimeStamp();
> this.familyMap.putAll(d.getFamilyCellMap());
> this.durability = d.durability;
> }
> {code}
> should copy the attributes also. Similar bug was raised for Put also. I remember because I found while debugging an MR issue. Now while checking another MR issue found for delete it has not been done.
--
This message was sent by Atlassian JIRA
(v6.2#6252)