[ https://issues.apache.org/jira/browse/HBASE-15698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318274#comment-15318274 ]
Hudson commented on HBASE-15698: -------------------------------- SUCCESS: Integrated in HBase-1.2 #643 (See [https://builds.apache.org/job/HBase-1.2/643/]) HBASE-15698 Increment TimeRange not serialized to server (Ted Yu) (apurtell: rev 8507446891a5e3506f4f585811aaeecab5079adf) * hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestIncrementTimeRange.java * hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java > 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: 2.0.0, 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, 15698.v4.txt, 15698.v4.txt, 15698.v5.txt, 15698.v6.txt, > 15698.v7.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)