phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3413) Ineffective null check in LiteralExpression#newConstant()
Date Wed, 04 Jan 2017 07:37:58 GMT


Hadoop QA commented on PHOENIX-3413:

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

    {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 43 warning messages.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit 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:

     {color:red}-1 core zombie tests{color}.  There are 1 zombie test(s): 	at

Test results:
Javadoc warnings:
Console output:

This message is automatically generated.

> Ineffective null check in LiteralExpression#newConstant()
> ---------------------------------------------------------
>                 Key: PHOENIX-3413
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.9.1
>            Reporter: Ted Yu
>            Assignee: Kevin Liew
>            Priority: Minor
>             Fix For: 4.10.0
>         Attachments: PHOENIX-3413.2.patch, PHOENIX-3413.patch
> {code}
>         if (maxLength == null) {
>             maxLength = type == null || !type.isFixedWidth() ? null : type.getMaxLength(value);
>         }
> {code}
> The null check for type is ineffective - type is de-referenced in various places prior
to the above check.

This message was sent by Atlassian JIRA

View raw message