[ 
https://issues.apache.org/jira/browse/SPARK-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124999#comment-14124999
 ] 

Jyotiska NK edited comment on SPARK-1087 at 9/7/14 6:33 PM:
------------------------------------------------------------

We initially thought this would be a good feature to add going forward. But 
after the PR was merged, it was abandoned. Also, PR 581 was created in the 
incubator github repo. In the new one, it was [PR 
#34|https://github.com/apache/spark/pull/34]. If it is a relevant feature, I 
can submit a PR for this.


was (Author: jyotiska):
We initially thought this would be a good feature to add going forward. But 
after the PR was merged, it was abandoned. Also, PR 581 was created in the 
incubator github repo. In the new one, it was [PR 
#34](https://github.com/apache/spark/pull/34). If it is a relevant feature, I 
can submit a PR for this.

> Separate file for traceback and callsite related functions
> ----------------------------------------------------------
>
>                 Key: SPARK-1087
>                 URL: https://issues.apache.org/jira/browse/SPARK-1087
>             Project: Spark
>          Issue Type: New Feature
>          Components: PySpark
>            Reporter: Jyotiska NK
>
> Right now, _extract_concise_traceback() is written inside rdd.py which 
> provides the callsite information. But for 
> [SPARK-972](https://spark-project.atlassian.net/browse/SPARK-972) in PR #581, 
> we used the function from context.py. Also some issues were faced regarding 
> the return string format. 
> It would be a good idea to move the the traceback function from rdd and 
> create a separate file for future developments. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to