[
https://issues.apache.org/jira/browse/DRILL-4840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Parth Chandra closed DRILL-4840.
--------------------------------
Resolution: Not A Problem
Weirdly enough, logback does in fact log to console if something is wrong when
it is starting up.
http://stackoverflow.com/questions/3257154/how-to-prevent-logback-from-outputting-its-own-status-at-the-start-of-every-log
However, what I was seeing is the [INFO] messages from logback as it is
starting up. I updated my logback to suppress those and the problem is gone.
Closing this as it may be specific to my setup
> Sqlline prints log output to stdout on startup
> ----------------------------------------------
>
> Key: DRILL-4840
> URL: https://issues.apache.org/jira/browse/DRILL-4840
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Parth Chandra
> Assignee: Paul Rogers
>
> With the refactoring of drill scripts, sqlline has now started printing
> logging messages to stdout when it starts up. This messes up some users'
> scripts that invoke sqlline.
> See also, DRILL-2798 which was logged because end users had scripts that
> broke as a result of printing out additional information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
