[
https://issues.apache.org/jira/browse/SPARK-15015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267334#comment-15267334
]
John-Michael Reed commented on SPARK-15015:
-------------------------------------------
Also, since Scala Macros can execute print statements and essentially run
in their own little "universe" at compile time, macro code must be compiled
separate from and before application code.
If you create a maven/sbt task or something like that, remember to give
the macro code its own separate compilation unit and jar file and remember
to compile it before the code that imports it. If the macro code is already
in a jar file you don't have to worry about it.
> 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: [email protected]
For additional commands, e-mail: [email protected]
