[ 
https://issues.apache.org/jira/browse/PHOENIX-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157809#comment-15157809
 ] 

Hadoop QA commented on PHOENIX-2703:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12789059/PHOENIX-2703.patch
  against master branch at commit e4acd0cda4ad8f12db8331af39a9e32f4b81c223.
  ATTACHMENT ID: 12789059

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 6 new 
or modified tests.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 
19 warning messages.

    {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:
    +  private static Path writeInputFile(final Configuration c, final 
TestOptions opts) throws IOException {
+    RandomScanWithRangeTest(Configuration conf, Connection conn, TestOptions 
options, Status status) {
+    System.err.println(" oneCon          all the threads share the same 
connection. Default: False");
+    System.err.println(" bloomFilter      Bloom filter type, one of " + 
Arrays.toString(BloomType.values()));
+    System.err.println(" randomSleep     Do a random sleep before each get 
between 0 and entered value. Defaults: 0");
+          throw new IllegalArgumentException(rows + " and " + size + " are 
mutually exclusive arguments.");

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
     
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.ImmutableIndexWithStatsIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.StatsCollectorWithSplitsAndMultiCFIT

Test results: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/260//testReport/
Javadoc warnings: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/260//artifact/patchprocess/patchJavadocWarnings.txt
Console output: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/260//console

This message is automatically generated.

> Port HBase's PerformanceEvaluation to Phoenix
> ---------------------------------------------
>
>                 Key: PHOENIX-2703
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2703
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Minor
>         Attachments: PHOENIX-2703.patch
>
>
> I know Phoenix has the very capable Pherf tool but I wanted a test tool as 
> similar as possible to HBase's PerformanceEvaluation when making comparisons 
> between HBase-only and HBase+Phoenix clusters and clients. Therefore I took 
> HBase's PerformanceEvaluation, and replaced HBase API calls with JDBC 
> equivalents without touching code where not necessary. The result is a small 
> and independent test tool, useful even though we have Pherf. I have the write 
> tests and some of the read tests working and tested. I'll post a patch when 
> all read tests have been tested, and when I've had a chance to test 
> everything using a MR framework.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to