You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/04/30 11:07:12 UTC
[jira] [Commented] (SPARK-15015) Log statements lack file
name/number
[ https://issues.apache.org/jira/browse/SPARK-15015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265255#comment-15265255 ]
Sean Owen commented on SPARK-15015:
-----------------------------------
Hm, is it actually possible to know the line number at runtime? it's present in the bytecode but not sure how a logging API would reach it. Here, it's your IDE providing this info.
> Log statements lack file name/number
> ------------------------------------
>
> Key: SPARK-15015
> URL: https://issues.apache.org/jira/browse/SPARK-15015
> Project: Spark
> Issue Type: Improvement
> Components: Build
> Affects Versions: 1.6.1
> Environment: All
> Reporter: John-Michael Reed
> Priority: Trivial
> Labels: debug, log
>
> I would like it if the Apache Spark project had file names and line numbers in its log statements like this:
> http://i.imgur.com/4hvGQ0t.png
> The example uses my library, http://johnreedlol.github.io/scala-trace-debug/, but https://github.com/lihaoyi/sourcecode is also useful for this purpose.
> The real benefit in doing this is because the user of an IDE can jump to the location of a log statement without having to set breakpoints.
> http://s29.postimg.org/ud0knou1j/debug_Screenshot_Crop.png
> Note that the arrow will go to the next log statement if each log statement is hyperlinked.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org