[
https://issues.apache.org/jira/browse/LIVY-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-116:
----------------------------
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.
> Use scala logging instead of "Logging" trait
> --------------------------------------------
>
> Key: LIVY-116
> URL: https://issues.apache.org/jira/browse/LIVY-116
> Project: Livy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.2
> Reporter: Marcelo Masiero Vanzin
> Priority: Major
> Fix For: 0.10.0
>
>
> After we switch to Scala 2.11, we should look at
> https://github.com/typesafehub/scala-logging. The {{Logging}} trait is a
> little annoying in that its methods sometimes clash, and require ugly
> workaround (like having a separate object just to provide logging).
> Also, the logging library is faster (because it uses macros and thus avoids
> instantiating a small closure for each logging call).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
