phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-5187) Avoid using FileInputStream and FileOutputStream
Date Mon, 11 Mar 2019 20:51:00 GMT


Hadoop QA commented on PHOENIX-5187:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against 4.x-HBase-1.3 branch at commit 26d3734d3c2a05c56e92a0ea09a99fd90059f568.
  ATTACHMENT ID: 12962013

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

> Avoid using FileInputStream and FileOutputStream 
> -------------------------------------------------
>                 Key: PHOENIX-5187
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 4.14.1
>            Reporter: Aman Poonia
>            Assignee: Aman Poonia
>            Priority: Major
>         Attachments: PHOENIX-5187-4.x-HBase-1.3.patch
> Avoid using FileInputStream and FileOutputStream because of
> []
> The file objects doesnot get cleaned up even if we close it until full GC happens
> This has been resolved in jdk10
> A quick workaround is to use File.newInputStream and Files.newOutputStream

This message was sent by Atlassian JIRA

View raw message