hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-15698) Increment TimeRange not serialized to server
Date Fri, 03 Jun 2016 16:58:59 GMT

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

Andrew Purtell updated HBASE-15698:
-----------------------------------
         Assignee: Ted Yu  (was: Sean Busbey)
    Fix Version/s:     (was: 1.0.4)
                   1.4.0

Ok, I'm going to push this through later today, and it's Ted's patch so I'm reassigning the
issue. My apologies for how this ends up yanking this out from underneath you [~busbey]. I
don't see a better path forward unless you have your own patch in a committable state I can
push up instead. 

> Increment TimeRange not serialized to server
> --------------------------------------------
>
>                 Key: HBASE-15698
>                 URL: https://issues.apache.org/jira/browse/HBASE-15698
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.2.0, 1.3.0
>            Reporter: James Taylor
>            Assignee: Ted Yu
>            Priority: Blocker
>              Labels: phoenix
>             Fix For: 1.3.0, 1.4.0, 1.2.2, 0.98.20, 1.1.6
>
>         Attachments: 15698-suggest.txt, 15698.v1.txt, 15698.v2.txt, 15698.v3.txt, HBASE-15698.1.patch
>
>
> Before HBase-1.2, the Increment TimeRange set on the client was serialized over to the
server. As of HBase 1.2, this appears to no longer be true, as my preIncrement coprocessor
always gets HConstants.LATEST_TIMESTAMP as the value of increment.getTimeRange().getMax()
regardless of what the client has specified.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message