[ https://issues.apache.org/jira/browse/HBASE-15698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15292257#comment-15292257 ]
Sean Busbey commented on HBASE-15698: ------------------------------------- [~jamestaylor], could you or someone else from the phoenix community either take a look or walk me through the pieces of customization phoenix has on the write path? I've been stepping through phoenix + hbase for this, but I have yet to find where the timerange handling is different from 1.1 to 1.2. > 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.2.2 > > Attachments: 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)