[jira] [Commented] (HBASE-15698) Increment TimeRange not serialized to server

["Andrew Purtell (JIRA)" <ji...@apache.org>]

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

Andrew Purtell commented on HBASE-15698:
----------------------------------------

This is blocking releases, at least the current 0.98 RC. It looks like this has stalled because one committer stomped on another's toes (Ted - you should apologize). I'm inclined to hold my nose and commit this everywhere to unblock it. Objections?

> 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: Sean Busbey
>            Priority: Blocker
>              Labels: phoenix
>             Fix For: 1.3.0, 1.0.4, 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)