[
https://issues.apache.org/jira/browse/HBASE-15698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255118#comment-15255118
]
James Taylor commented on HBASE-15698:
--------------------------------------
Yes, on our master branch at this commit:
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=0fbce9cd3122a16a890926e0b0042931ae8e03c4
The test that fails is PointInTimeQuery.testPointInTimeSequence(), but it'd be
much easier to repro in a standalone HBase test that calls
Increment.setTimeRange() on the client and then attempts to get the time range
in a coprocessor on the server side.
> 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
> Reporter: James Taylor
> Labels: phoenix
>
> 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)
