[
https://issues.apache.org/jira/browse/SPARK-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045325#comment-15045325
]
Justin Bailey commented on SPARK-8118:
--------------------------------------
Did some research and Parquet uses java.util.logging. You can disable the
chatty output by creating a properties file with these contents:
{noformat}
org.apache.parquet.handlers=java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level=SEVERE
{noformat}
And then passing the path of the file to Spark when the application is
submitted. Assuming the file lives in /tmp/parquet.logging.properties (of
course, that needs to be available on all worker nodes):
{noformat}
spark-submit \
--conf
spark.driver.extraJavaOptions="-Djava.util.logging.config.file=/tmp/parquet.logging.properties"
\
--conf
spark.executor.extraJavaOptions="-Djava.util.logging.config.file=/tmp/parquet.logging.properties"
\
...
{noformat}
> Turn off noisy log output produced by Parquet 1.7.0
> ---------------------------------------------------
>
> Key: SPARK-8118
> URL: https://issues.apache.org/jira/browse/SPARK-8118
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 1.4.1, 1.5.0
> Reporter: Cheng Lian
> Assignee: Cheng Lian
> Priority: Minor
> Fix For: 1.5.0
>
>
> Parquet 1.7.0 renames package name to "org.apache.parquet", need to adjust
> {{ParquetRelation.enableLogForwarding}} accordingly to avoid noisy log output.
> A better approach than simply muting these log lines is to redirect Parquet
> logs via SLF4J, so that we can handle them consistently. In general these
> logs are very useful. Esp. when used to diagnosing Parquet memory issue and
> filter push-down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
