Return-Path: X-Original-To: apmail-crunch-dev-archive@www.apache.org Delivered-To: apmail-crunch-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3828111A3E for ; Mon, 7 Jul 2014 01:11:34 +0000 (UTC) Received: (qmail 61373 invoked by uid 500); 7 Jul 2014 01:11:34 -0000 Delivered-To: apmail-crunch-dev-archive@crunch.apache.org Received: (qmail 61324 invoked by uid 500); 7 Jul 2014 01:11:34 -0000 Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@crunch.apache.org Delivered-To: mailing list dev@crunch.apache.org Received: (qmail 61307 invoked by uid 500); 7 Jul 2014 01:11:34 -0000 Delivered-To: apmail-incubator-crunch-dev@incubator.apache.org Received: (qmail 61302 invoked by uid 99); 7 Jul 2014 01:11:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jul 2014 01:11:33 +0000 Date: Mon, 7 Jul 2014 01:11:33 +0000 (UTC) From: "Josh Wills (JIRA)" To: crunch-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CRUNCH-435) Cleaner controls for configuring and initializing the SparkContext and runtime Configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)