You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Ismaël Mejía (JIRA)" <ji...@apache.org> on 2016/05/31 10:16:12 UTC
[jira] [Commented] (BEAM-313) Enable the use of an existing spark
context with the SparkPipelineRunner
[ https://issues.apache.org/jira/browse/BEAM-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307533#comment-15307533 ]
Ismaël Mejía commented on BEAM-313:
-----------------------------------
[~amitsela] What do you think about this ? The use case is not pure Beam, but in practice it makes sense in particular to have something like spark-job-server.
> Enable the use of an existing spark context with the SparkPipelineRunner
> ------------------------------------------------------------------------
>
> Key: BEAM-313
> URL: https://issues.apache.org/jira/browse/BEAM-313
> Project: Beam
> Issue Type: New Feature
> Reporter: Abbass Marouni
>
> The general use case is that the SparkPipelineRunner creates its own Spark context and uses it for the pipeline execution.
> Another alternative is to provide the SparkPipelineRunner with an existing spark context. This can be interesting for a lot of use cases where the Spark context is managed outside of beam (context reuse, advanced context management, spark job server, ...).
> code sample : https://github.com/amarouni/incubator-beam/commit/fe0bb517bf0ccde07ef5a61f3e44df695b75f076
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)