phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-5051) ScanningResultIterator metric "RowsScanned" not set
Date Mon, 03 Dec 2018 05:36:00 GMT


Hadoop QA commented on PHOENIX-5051:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against master branch at commit 52b563d70830454609ad416ee8dd271e37eeeb70.
  ATTACHMENT ID: 12950329

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler 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:red}-1 core tests{color}.  The patch failed these unit tests:

Test results:
Release audit warnings:
Console output:

This message is automatically generated.

> ScanningResultIterator metric "RowsScanned" not set
> ---------------------------------------------------
>                 Key: PHOENIX-5051
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0, 4.14.1
>            Reporter: Chen Feng
>            Priority: Major
>             Fix For: 4.15.0, 5.1.0, 4.14.2
>         Attachments: PHOENIX-5051-v1.patch, PHOENIX-5051-v2.patch
> in ScanningResultIterator, the metric "RowsScanned" was not set, while "RowsFiltered"
was set twice

This message was sent by Atlassian JIRA

View raw message