[jira] [Commented] (HBASE-13370) PE tool could give option for using Explicit Column Tracker which leads to seeks

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on HBASE-13370:
-----------------------------------

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

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

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

    {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions (2.4.1 2.5.2 2.6.0)

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

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

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

    {color:green}+1 checkstyle{color}.  The applied patch does not increase the total number of checkstyle errors

    {color:green}+1 findbugs{color}.  The patch does not introduce any  new Findbugs (version 2.0.3) warnings.

    {color:red}-1 release audit{color}.  The applied patch generated 1 release audit warnings (more than the master's current 0 warnings).

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

  {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:
     

     {color:red}-1 core zombie tests{color}.  There are 2 zombie test(s): 	at org.apache.hadoop.hbase.coprocessor.TestRegionServerObserver.testCoprocessorHooksInRegionsMerge(TestRegionServerObserver.java:100)
	at org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.clearDB(AbstractTestWithStaticConfiguration.java:434)

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/13514//testReport/
Release audit warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/13514//artifact/patchprocess/patchReleaseAuditWarnings.txt
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/13514//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/13514//artifact/patchprocess/checkstyle-aggregate.html

  Javadoc warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/13514//artifact/patchprocess/patchJavadocWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/13514//console

This message is automatically generated.

> PE tool could give option for using Explicit Column Tracker which leads to seeks
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-13370
>                 URL: https://issues.apache.org/jira/browse/HBASE-13370
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 1.0.0, 1.0.1
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>         Attachments: HBASE-13370.patch
>
>
> Currently in PE tool all the scans and gets adds explicitly the columns to be scanned.  The tool by default adds only one Qualifier.  Doing this addColumns leads to Explicit Column Tracker which does seeks frequently. If we want to know a simple scan performance as a basic scenario then we should have the option to add this columns explicitly.



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