You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Gabor Szadovszky (JIRA)" <ji...@apache.org> on 2018/04/21 12:39:03 UTC

[jira] [Updated] (PARQUET-305) Logger instantiated for package org.apache.parquet may be GC-ed

     [ https://issues.apache.org/jira/browse/PARQUET-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabor Szadovszky updated PARQUET-305:
-------------------------------------
    Fix Version/s: 1.8.2

> Logger instantiated for package org.apache.parquet may be GC-ed
> ---------------------------------------------------------------
>
>                 Key: PARQUET-305
>                 URL: https://issues.apache.org/jira/browse/PARQUET-305
>             Project: Parquet
>          Issue Type: Bug
>          Components: parquet-mr
>    Affects Versions: 1.7.0
>            Reporter: Cheng Lian
>            Assignee: Ryan Blue
>            Priority: Minor
>             Fix For: 1.9.0, 1.8.2
>
>
> This ticket is derived from SPARK-8122.
> According to Javadoc of [{{java.util.Logger}}|https://docs.oracle.com/javase/6/docs/api/java/util/logging/Logger.html]:
> {quote}
> It is important to note that the Logger returned by one of the getLogger factory methods may be garbage collected at any time if a strong reference to the Logger is not kept.
> {quote}
> However, the only reference to [the {{Logger}} created for package {{org.apache.parquet}}|https://github.com/apache/parquet-mr/blob/apache-parquet-1.7.0/parquet-common/src/main/java/org/apache/parquet/Log.java#L58] goes out of scope outside the static initialization block, and thus is possible to be garbage collected.
> More details can be found in [this comment|https://issues.apache.org/jira/browse/SPARK-8122?focusedCommentId=14574419&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14574419].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)