You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Haowei Yu (JIRA)" <ji...@apache.org> on 2019/08/01 15:56:00 UTC

[jira] [Updated] (ARROW-6099) [JAVA] Has the ability to not using slf4j logging framework

     [ https://issues.apache.org/jira/browse/ARROW-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Haowei Yu updated ARROW-6099:
-----------------------------
    Description: 
Currently, the java library directly calls slf4j api, and there is no abstract layer. This leads to user need to install slf4j as a requirement even if we don't use slf4j at all. 

 

It is best if you can change the slf4j dependency scope to provided and log content only if slf4j jar file is provided at runtime.

  was:
Currently, the java library directly calls slf4j api, and there is no abstract layer. This leads to user need to install slf4j as a requirement even if we don't use slf4j at all. 

 

It is best if you can change the slf4j dependency to provided and log content only if slf4j jar file is provided at runtime.


> [JAVA] Has the ability to not using slf4j logging framework
> -----------------------------------------------------------
>
>                 Key: ARROW-6099
>                 URL: https://issues.apache.org/jira/browse/ARROW-6099
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Java
>    Affects Versions: 0.14.1
>            Reporter: Haowei Yu
>            Priority: Major
>
> Currently, the java library directly calls slf4j api, and there is no abstract layer. This leads to user need to install slf4j as a requirement even if we don't use slf4j at all. 
>  
> It is best if you can change the slf4j dependency scope to provided and log content only if slf4j jar file is provided at runtime.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)