[
https://issues.apache.org/jira/browse/SPARK-7204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518047#comment-14518047
]
Apache Spark commented on SPARK-7204:
-------------------------------------
User 'pwendell' has created a pull request for this issue:
https://github.com/apache/spark/pull/5757
> Call sites in UI are not accurate for DataFrame operations
> ----------------------------------------------------------
>
> Key: SPARK-7204
> URL: https://issues.apache.org/jira/browse/SPARK-7204
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.3.1
> Reporter: Patrick Wendell
> Assignee: Patrick Wendell
> Priority: Critical
>
> Spark core computes callsites by climbing up the stack until we reach the
> stack frame at the boundary of user code and spark code. The way we compute
> whether a given frame is internal (Spark) or user code does not work
> correctly with the new dataframe API.
> Once the scope work goes in, we'll have a nicer way to express units of
> operator scope, but until then there is a simple fix where we just make sure
> the SQL internal classes are also skipped as we climb up the stack.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
