[ https://issues.apache.org/jira/browse/HBASE-15698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261281#comment-15261281 ]
Andrew Purtell commented on HBASE-15698: ---------------------------------------- Unless I misunderstand what happened this is a wire compatibility breach. No more 1.2 or any subsequent 1.x releases should go out until it is fixed. I made this issue a blocker. We can document errata for already released versions of 1.2 if need be. [~busbey] [~mantonov] > 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 > Priority: Blocker > Labels: phoenix > Fix For: 1.3.0, 1.2.2 > > > 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)