[
https://issues.apache.org/jira/browse/HBASE-15698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315599#comment-15315599
]
Andrew Purtell commented on HBASE-15698:
----------------------------------------
bq. Looking back on the test in v3, it doesn't make sense to send two
Increments for the same row, family and qualifier in one batch.
Maybe not for the purposes of this test but why wouldn't we expect increments
in batch to all be processed and sum to the expected amount even if to the same
location?
bq. Can you elaborate a bit more on where the injection takes place ?
In test setup you'd do:
{code}
// static or test class field
ManualEnvironmentEdge me;
// somewhere in init
me = new ManualEnvironmentEdge();
EnvironmentEdgeManager.injectEdge(me);
{code}
and then use the reference to 'me' to adjust the clock for the test cases.
> 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, 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)
