[
https://issues.apache.org/jira/browse/HBASE-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranav Khaitan updated HBASE-2854:
----------------------------------
Attachment: TimerangeAlltime.patch
The tests were broken because the Timestamp was not being set and it used to
take the default value which is Long.Max_Value. The default timerange is 0 to
Long.Max_Value (exclusive) so the default timestamp will never exist within
default timerange. I created a patch which uses the existing extra variable to
handle this case. I don't think this change is required but some tests in
future which do not set the timestamp may fail again if this is not used.
Note: Even after this patch, there is no way we can create a finite timerange
which includes Long.Max_Value .
> broken tests on trunk
> ---------------------
>
> Key: HBASE-2854
> URL: https://issues.apache.org/jira/browse/HBASE-2854
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.89.20100621
> Reporter: ryan rawson
> Fix For: 0.90.0
>
> Attachments: TimerangeAlltime.patch
>
>
> the following tests are broken:
> >>><<<
> >>>org.apache.hadoop.hbase.regionserver.TestStore.testIncrementColumnValue_ICVDuringFlush
> All of the TestQueryMatcher tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
