hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15698) Increment TimeRange not serialized to server
Date Wed, 27 Apr 2016 07:44:13 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259721#comment-15259721
] 

Mikhail Antonov commented on HBASE-15698:
-----------------------------------------

[~jamestaylor] I didn't look at this one (but appears enough people been looking at it) -
how bad it is / much do you want that resolves in 1.3 :) ? I'm planning to start rolling RCs
sometimes next week. Feel free do set fixVersion to 1.3 is that's critical and there's some
bandwidth here to work on it...

> 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
>            Reporter: James Taylor
>              Labels: phoenix
>
> 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