[jira] [Comment Edited] (SPARK-2377) Create a Python API for Spark Streaming
[ https://issues.apache.org/jira/browse/SPARK-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14134210#comment-14134210 ] Jyotiska NK edited comment on SPARK-2377 at 9/15/14 6:00 PM: - I have been watching the work going on PR #11 for a while. Is there any way to contribute to this? was (Author: jyotiska): I have been watching the work going on PR #11. Is there any way to contribute to this? Create a Python API for Spark Streaming --- Key: SPARK-2377 URL: https://issues.apache.org/jira/browse/SPARK-2377 Project: Spark Issue Type: New Feature Components: PySpark, Streaming Reporter: Nicholas Chammas Assignee: Kenichi Takagiwa [Spark Streaming|http://spark.apache.org/docs/latest/streaming-programming-guide.html] currently offers APIs in Scala and Java. It would be great feature add to have a Python API as well. This is probably a large task that will span many issues if undertaken. This ticket should provide some place to track overall progress towards an initial Python API for Spark Streaming. -- 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
[jira] [Commented] (SPARK-2377) Create a Python API for Spark Streaming
[ https://issues.apache.org/jira/browse/SPARK-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14134210#comment-14134210 ] Jyotiska NK commented on SPARK-2377: I have been watching the work going on PR #11. Is there any way to contribute to this? Create a Python API for Spark Streaming --- Key: SPARK-2377 URL: https://issues.apache.org/jira/browse/SPARK-2377 Project: Spark Issue Type: New Feature Components: PySpark, Streaming Reporter: Nicholas Chammas Assignee: Kenichi Takagiwa [Spark Streaming|http://spark.apache.org/docs/latest/streaming-programming-guide.html] currently offers APIs in Scala and Java. It would be great feature add to have a Python API as well. This is probably a large task that will span many issues if undertaken. This ticket should provide some place to track overall progress towards an initial Python API for Spark Streaming. -- 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
[jira] [Commented] (SPARK-1087) Separate file for traceback and callsite related functions
[ https://issues.apache.org/jira/browse/SPARK-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14124999#comment-14124999 ] Jyotiska NK commented on SPARK-1087: 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. 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: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Comment Edited] (SPARK-1087) Separate file for traceback and callsite related functions
[ https://issues.apache.org/jira/browse/SPARK-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14124999#comment-14124999 ] Jyotiska NK edited comment on SPARK-1087 at 9/7/14 6:32 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. 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: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Comment Edited] (SPARK-1087) Separate file for traceback and callsite related functions
[ https://issues.apache.org/jira/browse/SPARK-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
