You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Steve Scaffidi (JIRA)" <ji...@apache.org> on 2017/08/08 16:39:00 UTC

[jira] [Commented] (PARQUET-401) Deprecate Log and move to SLF4J Logger

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

Steve Scaffidi commented on PARQUET-401:
----------------------------------------

Just in case it helps anybody... when using Hive with Parquet in CDH 5.x, I found a work-around for unwanted log output from Parquet in the container logs: https://issues.apache.org/jira/browse/SPARK-4412?focusedCommentId=16118403

> Deprecate Log and move to SLF4J Logger
> --------------------------------------
>
>                 Key: PARQUET-401
>                 URL: https://issues.apache.org/jira/browse/PARQUET-401
>             Project: Parquet
>          Issue Type: Bug
>          Components: parquet-mr
>    Affects Versions: 1.8.1
>            Reporter: Ryan Blue
>
> The current Log class is intended to allow swapping out logger back-ends, but SLF4J already does this. It also doesn't expose as nice of an API as SLF4J, which can handle formatting to avoid the cost of building log messages that won't be used. I think we should deprecate the org.apache.parquet.Log class and move to using SLF4J directly, instead of wrapping SLF4J (PARQUET-305).
> This will require deprecating the current Log class and replacing the current uses of it with SLF4J.



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