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

Hadoop QA commented on HADOOP-10364:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  5s{color} 
| {color:red} HADOOP-10364 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-10364 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12665692/HADOOP-10364.2.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/11106/console |
| Powered by | Apache Yetus 0.4.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> JsonGenerator in Configuration#dumpConfiguration() is not closed
> ----------------------------------------------------------------
>
>                 Key: HADOOP-10364
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10364
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>            Reporter: Ted Yu
>              Labels: BB2015-05-TBR
>         Attachments: HADOOP-10364.2.patch, HADOOP-10364.patch
>
>
> {code}
>     JsonGenerator dumpGenerator = dumpFactory.createJsonGenerator(out);
> {code}
> dumpGenerator is not closed in Configuration#dumpConfiguration()
> Looking at the source code of 
> org.codehaus.jackson.impl.WriterBasedGenerator#close(), there is more than 
> flushing the buffer.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to