[
https://issues.apache.org/jira/browse/PARQUET-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058745#comment-15058745
]
Ryan Blue commented on PARQUET-401:
-----------------------------------
[[email protected]], thanks for bringing this up. It sounds like the issue
you're raising about the move to use the SLF4J API, but is about PARQUET-369. I
just want to make sure that the discussion doesn't really affect how or when
Parquet MR moves.
For the issue you brought up with PARQUET-369, I'm going to go ahead and
respond on that issue so it's easy to follow later when I completely forget
everything. :)
> 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.3.4#6332)
