[
https://issues.apache.org/jira/browse/FLINK-18284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134995#comment-17134995
]
appleyuchi edited comment on FLINK-18284 at 6/14/20, 1:22 AM:
--------------------------------------------------------------
1.you may know that last official fix is only for start-scala-shell.sh,not for
log4j.properties.
are you sure your log4j.propertires is left as default when you test it?
2.This is already 1.11 code from newest github.
start-scala-shell.sh->xxx.xml->log4j.properties,
this is the flow.
3. if you think it's not correct and useless,
then what's the correct configuration of log4j.properties?
we are not familiar with configuration of it,py/scala users are a large part.
was (Author: appleyuchi):
1.you may know that last official fix is only for start-scala-shell.sh,not for
log4j.properties.
are you sure your log4j.propertires is left as default when you test it?
2.This is already 1.11 code from newest github.
start-scala-shell.sh->xxx.xml->log4j.properties,
this is the flow.
3. if you think it's not correct and useless,
then what's the correct configuration of log4j.properties?
you can not assume that users are familiar with configuration of it,py/scala
users are a large part.
> No appenders could be found for logger
> ---------------------------------------
>
> Key: FLINK-18284
> URL: https://issues.apache.org/jira/browse/FLINK-18284
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.11.1
> Reporter: appleyuchi
> Priority: Major
>
> start-scala-shell.sh local
> Starting Flink Shell:
> log4j:WARN No appenders could be found for logger
> (org.apache.flink.configuration.GlobalConfiguration).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
>
> what's the configuration to fix this warning,it's annoying.
> PS:
> configuration in log4j.properties did not work.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
