You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Josh Wills (JIRA)" <ji...@apache.org> on 2014/07/07 03:11:33 UTC
[jira] [Resolved] (CRUNCH-435) Cleaner controls for configuring and
initializing the SparkContext and runtime Configuration
[ https://issues.apache.org/jira/browse/CRUNCH-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Wills resolved CRUNCH-435.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.11.0
0.8.4
Fixed in master and 0.8.
> Cleaner controls for configuring and initializing the SparkContext and runtime Configuration
> ---------------------------------------------------------------------------------------------
>
> Key: CRUNCH-435
> URL: https://issues.apache.org/jira/browse/CRUNCH-435
> Project: Crunch
> Issue Type: Bug
> Reporter: Josh Wills
> Fix For: 0.8.4, 0.11.0
>
> Attachments: CRUNCH-435.patch
>
>
> I spent a good chunk of the week working with the SparkPipeline implementation, and I came up with a few improvements to the flow that controls how the JavaSparkContext gets created when we're not given one directly.
> The main idea is to re-use the Pipeline's Configuration object to specify any of the critical spark-specific configuration options (e.g., memory allocations) in a SparkConf instance before constructing the JavaSparkContext.
--
This message was sent by Atlassian JIRA
(v6.2#6252)