[ 
https://issues.apache.org/jira/browse/HIVE-24591?focusedWorklogId=536860&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-536860
 ]

ASF GitHub Bot logged work on HIVE-24591:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 16/Jan/21 20:07
            Start Date: 16/Jan/21 20:07
    Worklog Time Spent: 10m 
      Work Description: belugabehr commented on pull request #1833:
URL: https://github.com/apache/hive/pull/1833#issuecomment-761624674


   Not to self, make scope for logger `runtime`


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 536860)
    Time Spent: 1.5h  (was: 1h 20m)

> Move Beeline To SLF4J Simple Logger
> -----------------------------------
>
>                 Key: HIVE-24591
>                 URL: https://issues.apache.org/jira/browse/HIVE-24591
>             Project: Hive
>          Issue Type: Improvement
>          Components: Beeline
>            Reporter: David Mollitor
>            Assignee: David Mollitor
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> To make beeline as simple as possible, move its SLF4J logger implementation 
> to SLFJ-Simple logger.  This will allow users to change the logging level 
> simply on the command line.  Currently uses must create a Log4J configuration 
> file which is way too advance/cumbersome for a data analyst that just wants 
> to use SQL (and do some minor troubleshooting)
> {code:none}
> export HADOOP_CLIENT_OPTS="-Dorg.slf4j.simpleLogger.defaultLogLevel=debug"
> beeline ...
> {code}
> http://www.slf4j.org/api/org/slf4j/impl/SimpleLogger.html



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

Reply via email to