[jira] [Resolved] (PHOENIX-288) Phoenix long type and Hbase incrementColumnValue

["Gabriel Reid (JIRA)" <ji...@apache.org>]

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

Gabriel Reid resolved PHOENIX-288.
----------------------------------

    Resolution: Fixed

Bulk resolve of closed issues imported from GitHub. This status was reached by first re-opening all closed imported issues and then resolving them in bulk.

> Phoenix long type and Hbase incrementColumnValue
> ------------------------------------------------
>
>                 Key: PHOENIX-288
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-288
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: maillard
>
> Hi everyone
> I am running an M/R job to fill an Hbase table that I have previously declared through Phoenix. 
> During this job I increment some columns.
> During the query phase these incremented values I get back are inverted, I mean instead of 1 I get -95000 or to be more precises I get Long.maxvalue - value in table.
> In the encode and decode long in the PdataType the sign bit is flipped. That is fine within phoenix since the reverse is done when reading and writing. But the Hbase incrementColumnvalue does not seem to have the same behaviour.
> On a similar note  when I try to access a phoenix upserted hbase table through the standard Hbase API my LONG or INT will be flipped
> regardes



--
This message was sent by Atlassian JIRA
(v6.2#6252)