[
https://issues.apache.org/jira/browse/HADOOP-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546952
]
Hadoop QA commented on HADOOP-2296:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12370378/2296.patch
against trunk revision r599586.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests -1. The patch failed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1210/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1210/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1210/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1210/console
This message is automatically generated.
> hbase shell: phantom columns show up from select command
> --------------------------------------------------------
>
> Key: HADOOP-2296
> URL: https://issues.apache.org/jira/browse/HADOOP-2296
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Affects Versions: 0.15.0
> Reporter: Michael Bieniosek
> Attachments: 2296.patch
>
>
> {code}
> Hbase> select * from hbase_test where row='2';
> +--------------------------------------+--------------------------------------+
> | Column | Cell
> |
> +--------------------------------------+--------------------------------------+
> | test:a | a
> |
> +--------------------------------------+--------------------------------------+
> | test:c | c
> |
> +--------------------------------------+--------------------------------------+
> 2 row(s) in set (0.00 sec)
> Hbase> select * from hbase_test where row='1';
> +--------------------------------------+--------------------------------------+
> | Column | Cell
> |
> +--------------------------------------+--------------------------------------+
> | test:a | a
> |
> +--------------------------------------+--------------------------------------+
> | test:b | b
> |
> +--------------------------------------+--------------------------------------+
> 2 row(s) in set (0.00 sec)
> Hbase> select * from hbase_test;
> +-------------------------+-------------------------+-------------------------+
> | Row | Column | Cell
> |
> +-------------------------+-------------------------+-------------------------+
> | 1 | test:a | a
> |
> +-------------------------+-------------------------+-------------------------+
> | 1 | test:b | b
> |
> +-------------------------+-------------------------+-------------------------+
> | 2 | test:a | a
> |
> +-------------------------+-------------------------+-------------------------+
> | 2 | test:b | b
> |
> +-------------------------+-------------------------+-------------------------+
> | 2 | test:c | c
> |
> +-------------------------+-------------------------+-------------------------+
> 5 row(s) in set (0.14 sec)
> {code}
> Note the phantom value for test:b in row 2.
> I looked at the code, and it looks like SelectCommand.scanPrint incorrectly
> fails to call results.clear() every time it calls scan.next().
> However, I also think that the HScannerInterface.next(HStoreKey key,
> SortedMap<Text,byte[]> results) is confusing, since it requires the user to
> call results.clear() and key.clear() before calling next each time. Since
> the Iterable interface that provides the zero-arg next has been added, I
> suggest that it might be worthwhile to deprecate the two-arg next.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
