[
https://issues.apache.org/jira/browse/HBASE-10254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858967#comment-13858967
]
James Taylor commented on HBASE-10254:
--------------------------------------
I don't see this (or its KeyValue equivalent) in 0.94. Also, I'm using the
Phoenix serialized form for the increment amount, so if HBase uses
Bytes.toLong(byte[]) to get the increment, it won't work. I could manufacture
another Cell, but what I'd rather have is an API like this:
public Increment addColumn(byte[] family, byte[] qualifier, long amount, long
timestamp)
> Optionally return null when attempting to Increment KeyValue that doesn't
> exist
> -------------------------------------------------------------------------------
>
> Key: HBASE-10254
> URL: https://issues.apache.org/jira/browse/HBASE-10254
> Project: HBase
> Issue Type: Bug
> Reporter: James Taylor
>
> Instead of creating a new KeyValue starting from 0 when an Increment is done
> on a row that doesn't exist, we should optionally return null. A Get is
> already being done, so it's easy to detect this case. This can be done in a
> backward compatible manner if the behavior is done optionally. In addition,
> Increment does not allow me to specify the timestamp to use for the KeyValue.
> This should be added as well.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
