[
https://issues.apache.org/jira/browse/HBASE-9005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053404#comment-14053404
]
Hadoop QA commented on HBASE-9005:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12654273/HBASE-11317.patch
against trunk revision .
ATTACHMENT ID: 12654273
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 findbugs{color}. The patch appears to introduce 4 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+
xlink:href="http://blog.cloudera.com/blog/2013/09/how-to-test-hbase-applications-using-popular-tools/";>http://blog.cloudera.com/blog/2013/09/how-to-test-hbase-applications-using-popular-tools/</link>.
+ The following sections discuss JUnit, Mockito, MRUnit, and
HBaseTestingUtility. </para>
+ assertEquals(obj.getData1(), Bytes.toString(put.get(Bytes.toBytes("CF"),
Bytes.toBytes("CQ-1")).get(0).getValue()));
+ assertEquals(obj.getData2(), Bytes.toString(put.get(Bytes.toBytes("CF"),
Bytes.toBytes("CQ-2")).get(0).getValue()));</userinput>
+
xlink:href="https://github.com/junit-team/junit/wiki/Getting-started";>https://github.com/junit-team/junit/wiki/Getting-started</link>.
+
xlink:href="https://code.google.com/p/mockito/";>https://code.google.com/p/mockito/</link>.</para>
+
assertEquals(Bytes.toString(put.get(Bytes.toBytes("CF"),Bytes.toBytes("CQ-1")).get(0).getValue()),
"DATA-1");
+
assertEquals(Bytes.toString(put.get(Bytes.toBytes("CF"),Bytes.toBytes("CQ-2")).get(0).getValue()),
"DATA-2");
+ <para>This code populates <code>HBaseTestObj</code> with
âROWKEY-1â, âDATA-1â,
+ âDATA-2â as values. It then inserts the record into
the mocked table. The Put
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/9978//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9978//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9978//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9978//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9978//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9978//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9978//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9978//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9978//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9978//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9978//console
This message is automatically generated.
> Improve documentation around KEEP_DELETED_CELLS, time range scans, and delete
> markers
> -------------------------------------------------------------------------------------
>
> Key: HBASE-9005
> URL: https://issues.apache.org/jira/browse/HBASE-9005
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Reporter: Lars Hofhansl
> Assignee: Misty Stanley-Jones
> Priority: Minor
> Fix For: 0.99.0
>
> Attachments: 9005.txt, HBASE-11317.patch
>
>
> Without KEEP_DELETED_CELLS all timerange queries are broken if their range
> covers a delete marker.
> As some internal discussions with colleagues showed, this feature is not well
> understand and documented.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
