[jira] [Updated] (HBASE-10254) Optionally return null when attempting to Increment KeyValue that doesn't exist

["James Taylor (JIRA)" <ji...@apache.org>]

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

James Taylor updated HBASE-10254:
---------------------------------

    Description: 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.  (was: 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.)

> 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)