[
https://issues.apache.org/jira/browse/SPARK-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tathagata Das updated SPARK-11361:
----------------------------------
Description:
Currently, when a DStream sets the scope for RDD generated by it, that scope is
not allowed to be overridden by the RDD operations. So in case of
`DStream.foreachRDD`, all the RDDs generated inside the foreachRDD get the same
scope - `foreachRDD @ <time>`, as set by the `ForeachDStream`. So it is hard to
debug generated RDDs in the RDD DAG viz in the Spark UI.
This JIRA is to allow the RDD operations inside `DStream.transform` and
`DStream.foreachRDD` to append their own scopes to the earlier DStream scope.
> Show scopes of RDD operations inside DStream.foreachRDD and DStream.transform
> in DAG viz
> ----------------------------------------------------------------------------------------
>
> Key: SPARK-11361
> URL: https://issues.apache.org/jira/browse/SPARK-11361
> Project: Spark
> Issue Type: Improvement
> Components: Streaming
> Reporter: Tathagata Das
> Assignee: Tathagata Das
> Priority: Minor
>
> Currently, when a DStream sets the scope for RDD generated by it, that scope
> is not allowed to be overridden by the RDD operations. So in case of
> `DStream.foreachRDD`, all the RDDs generated inside the foreachRDD get the
> same scope - `foreachRDD @ <time>`, as set by the `ForeachDStream`. So it is
> hard to debug generated RDDs in the RDD DAG viz in the Spark UI.
> This JIRA is to allow the RDD operations inside `DStream.transform` and
> `DStream.foreachRDD` to append their own scopes to the earlier DStream scope.
--
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
