You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Reynold Xin (JIRA)" <ji...@apache.org> on 2015/06/05 04:45:38 UTC

[jira] [Updated] (SPARK-8122) A few problems in ParquetRelation.enableLogForwarding()

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

Reynold Xin updated SPARK-8122:
-------------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: SPARK-5463

> A few problems in ParquetRelation.enableLogForwarding()
> -------------------------------------------------------
>
>                 Key: SPARK-8122
>                 URL: https://issues.apache.org/jira/browse/SPARK-8122
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 1.5.0
>            Reporter: Konstantin Shaposhnikov
>
> _enableLogForwarding()_ should be updated after parquet 1.7.0 update , because name of the logger has been changed to `org.apache.parquet`. From parquet-mr Log:
> {code}
>     // add a default handler in case there is none
>     Logger logger = Logger.getLogger(Log.class.getPackage().getName());
> {code}
> Another problem with _enableLogForwarding()_ is that it doesn't hold to the created loggers that can be garbage collected and all configuration changes will be gone. From https://docs.oracle.com/javase/6/docs/api/java/util/logging/Logger.html javadocs:  _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._



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org