hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Gray (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-1563) incrementColumnValue does not write to WAL
Date Wed, 24 Jun 2009 22:17:07 GMT

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

Jonathan Gray updated HBASE-1563:

    Attachment: HBASE-1563-v4.patch

New patch that copies the existing KV instead of incrementing in-place.

This is now broken.  The CSLMap has the same behavior as the CSLSet.  Since the keys are considered
"equal" the values might be updated in the map (in this case meaningless) but they don't swap
the key with the new one (since it's equal).  It does not have the behavior we wanted, an
atomic put that replaces the Key in case of collisions.

> incrementColumnValue does not write to WAL
> ------------------------------------------
>                 Key: HBASE-1563
>                 URL: https://issues.apache.org/jira/browse/HBASE-1563
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.0
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>             Fix For: 0.20.0
>         Attachments: HBASE-1563-v1.patch, HBASE-1563-v2.patch, HBASE-1563-v3.patch, HBASE-1563-v4.patch
> Incrementing never writes to the WAL.  Under failure scenarios, you will lose all increments
since the last flush.
> Do we want to expose the option to the client as to whether to write to WAL or not?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message