[
https://issues.apache.org/jira/browse/LIVY-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-605:
----------------------------
Fix Version/s: 0.10.0
(was: 0.9.0)
This issue has been moved to the 0.10.0 release as part of a bulk update. If
you feel this is moved out inappropriately, feel free to provide justification
and reset the Fix Version to 0.9.0.
> Provide default Log4j initialization
> ------------------------------------
>
> Key: LIVY-605
> URL: https://issues.apache.org/jira/browse/LIVY-605
> Project: Livy
> Issue Type: Improvement
> Components: Core, Server
> Affects Versions: 0.6.0
> Reporter: Eli Treuherz
> Priority: Trivial
> Fix For: 0.10.0
>
>
> Presently, as far as I can tell, a new user must duplicate the
> log4j.properties.template file into log4j.properties in the conf dir for Livy
> to run, otherwise it writes
>
> {code:java}
> log4j:WARN No appenders could be found for logger
> (org.apache.livy.server.AccessManager).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> {code}
> to the log file and nothing else.
> It would be better to bundle the server, or the livy core, with a default
> log4j file that is initialised if no other one is present, [the same way
> Spark
> does|https://github.com/apache/spark/blob/25b97a41ceede7b99a5f835077de94b38743203a/core/src/main/scala/org/apache/spark/internal/Logging.scala#L119].
> This would make setting up Livy for the first time that bit more
> frictionless.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
