phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3856) StatementContext class constructor not honouring supplied scan object
Date Wed, 17 May 2017 08:40:04 GMT


Hadoop QA commented on PHOENIX-3856:

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

    {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 javadoc{color}.  The javadoc tool appears to have generated 47 warning messages.

    {color:red}-1 release audit{color}.  The applied patch generated 2 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:
Javadoc warnings:
Console output:

This message is automatically generated.

> StatementContext class  constructor not honouring supplied scan object
> ----------------------------------------------------------------------
>                 Key: PHOENIX-3856
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.10.0
>            Reporter: Maddineni Sukumar
>            Assignee: Maddineni Sukumar
>            Priority: Minor
>             Fix For: 4.11.0
>         Attachments: PHOENIX-3856.patch
> In below constructor  we are creating additional scan object instead of supplied scan
>  public StatementContext(PhoenixStatement statement, Scan scan) {
>         this(statement, FromCompiler.EMPTY_TABLE_RESOLVER, new Scan(), new SequenceManager(statement));
>     }

This message was sent by Atlassian JIRA

View raw message