[ https://issues.apache.org/jira/browse/HBASE-15698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316942#comment-15316942 ]
Sean Busbey commented on HBASE-15698: ------------------------------------- {quote} bq. Sean Busbey is on vacation this week Bah. I owe you a favor Sean Busbey as apology so please feel free to call it in whenever. {quote} No worries. Sorry I needed to disappear for a bit without any notice. FWIW, my plan on my return was just to commit whatever Ted had come up with as long as tests were passing. > 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, 15698.v4.txt, 15698.v4.txt, 15698.v5.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)