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

Steve Scaffidi commented on SPARK-4412:
---------------------------------------

Apologies - I just realized this is the JIRA for Spark, not Parquet! A 
spark-oriented workaround can be found on StackOverflow, here: 
https://stackoverflow.com/a/38344902/14186

> Parquet logger cannot be configured
> -----------------------------------
>
>                 Key: SPARK-4412
>                 URL: https://issues.apache.org/jira/browse/SPARK-4412
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.2.0, 1.3.1
>            Reporter: Jim Carroll
>
> The Spark ParquetRelation.scala code makes the assumption that the 
> parquet.Log class has already been loaded. If 
> ParquetRelation.enableLogForwarding executes prior to the parquet.Log class 
> being loaded then the code in enableLogForwarding has no affect.
> ParquetRelation.scala attempts to override the parquet logger but, at least 
> currently (and if your application simply reads a parquet file before it does 
> anything else with Parquet), the parquet.Log class hasn't been loaded yet. 
> Therefore the code in ParquetRelation.enableLogForwarding has no affect. If 
> you look at the code in parquet.Log there's a static initializer that needs 
> to be called prior to enableLogForwarding or whatever enableLogForwarding 
> does gets undone by this static initializer.
> The "fix" would be to force the static initializer to get called in 
> parquet.Log as part of enableForwardLogging. 
> PR will be forthcomming.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to