[jira] [Updated] (PHOENIX-6461) sqlline-thin does not include slf4j logging backend

["Istvan Toth (Jira)" <ji...@apache.org>]

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

Istvan Toth updated PHOENIX-6461:
---------------------------------
    Description: 
The Avatica client JAR that we use in the phoenix thin client JAR does not include and sfl4j backend.

This in itself is not a problem, as it allows dependent project to use their preferred backend.

However, we are not adding a backend in the sqlline-thin script either, which results in any log messages being dropped.

We should add a log implementation in the sqlline-thin script to the classpath.
Probably slf4j-simple would be the best choice.


  was:
The Avatica client JAR that we use in the phoenix thin client JAR does not include and sfl4j backend.

This in itself is not a problem, as it allows dependent project to use their preferred backend.

However, we are not a backend in the sqlline-thin backend either, which results in any log messages being dropped.

We should add a log implementation in the sqlline-thin script to the classpath.
Probably slf4j-simple would be the best choice.



> sqlline-thin does not include slf4j logging backend
> ---------------------------------------------------
>
>                 Key: PHOENIX-6461
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6461
>             Project: Phoenix
>          Issue Type: Bug
>          Components: queryserver
>            Reporter: Istvan Toth
>            Priority: Major
>
> The Avatica client JAR that we use in the phoenix thin client JAR does not include and sfl4j backend.
> This in itself is not a problem, as it allows dependent project to use their preferred backend.
> However, we are not adding a backend in the sqlline-thin script either, which results in any log messages being dropped.
> We should add a log implementation in the sqlline-thin script to the classpath.
> Probably slf4j-simple would be the best choice.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)