You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "David Mollitor (Jira)" <ji...@apache.org> on 2020/01/10 21:27:00 UTC
[jira] [Updated] (PARQUET-1752) Remove slf4j-log4j12 Binding from
parquet-protobuf Module
[ https://issues.apache.org/jira/browse/PARQUET-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Mollitor updated PARQUET-1752:
------------------------------------
Description:
{code:none}
Running org.apache.parquet.proto.ProtoInputOutputFormatTest
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/m2/org/slf4j/slf4j-log4j12/1.7.10/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/m2/org/slf4j/slf4j-simple/1.7.22/slf4j-simple-1.7.22.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
{code}
There are two bindings being included and it produces this warning. {{slf4j-log4j12}} is coming in as a transient dependency. There is also a log4j properties file in the test resources, but all it does is produce logging to the console. Just stick with the {{slf4j-simple}} logger for testing (which is already explicitly specified for testing)
was:
{code:none}
Running org.apache.parquet.proto.ProtoInputOutputFormatTest
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/m2/org/slf4j/slf4j-log4j12/1.7.10/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/m2/org/slf4j/slf4j-simple/1.7.22/slf4j-simple-1.7.22.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
{code}
There are two bindings being included and it produces this warning. This is also a log4j properties file in the test resources, but all it does is produce logging to the console. Just stick with the {{slf4j-simple}} logger for testing.
> Remove slf4j-log4j12 Binding from parquet-protobuf Module
> ---------------------------------------------------------
>
> Key: PARQUET-1752
> URL: https://issues.apache.org/jira/browse/PARQUET-1752
> Project: Parquet
> Issue Type: Improvement
> Reporter: David Mollitor
> Assignee: David Mollitor
> Priority: Minor
>
> {code:none}
> Running org.apache.parquet.proto.ProtoInputOutputFormatTest
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in [jar:file:/m2/org/slf4j/slf4j-log4j12/1.7.10/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [jar:file:/m2/org/slf4j/slf4j-simple/1.7.22/slf4j-simple-1.7.22.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> {code}
> There are two bindings being included and it produces this warning. {{slf4j-log4j12}} is coming in as a transient dependency. There is also a log4j properties file in the test resources, but all it does is produce logging to the console. Just stick with the {{slf4j-simple}} logger for testing (which is already explicitly specified for testing)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)