Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 154C419552 for ; Sat, 2 Apr 2016 05:56:32 +0000 (UTC) Received: (qmail 94543 invoked by uid 500); 2 Apr 2016 05:56:32 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 94497 invoked by uid 500); 2 Apr 2016 05:56:32 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 94487 invoked by uid 99); 2 Apr 2016 05:56:32 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Apr 2016 05:56:32 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id C3220C0CD5 for ; Sat, 2 Apr 2016 05:56:31 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.972 X-Spam-Level: X-Spam-Status: No, score=0.972 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id N46XFPcBBApR for ; Sat, 2 Apr 2016 05:56:29 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 79F2E5F247 for ; Sat, 2 Apr 2016 05:56:28 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id BA5812450806 for ; Fri, 1 Apr 2016 22:44:48 -0700 (PDT) Date: Fri, 1 Apr 2016 22:42:54 -0700 (PDT) From: F7753 To: user@ignite.apache.org Message-ID: <1459575774450-3874.post@n6.nabble.com> In-Reply-To: <1459568306602-3873.post@n6.nabble.com> References: <1459508672304-3854.post@n6.nabble.com> <1459516182417-3860.post@n6.nabble.com> <1459543053403-3870.post@n6.nabble.com> <1459568306602-3873.post@n6.nabble.com> Subject: Re: Should Ignition.start() method to be called in a spark-igniteRDD app? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit What makes me very confused is that when I use ignite to run a spark word count app, it did not ask me to call 'Ignition.start()', while I use igniteRDD to cache table and just run a spark streaming app, the console throw the exception. What's the difference? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Should-Ignition-start-method-to-be-called-in-a-spark-igniteRDD-app-tp3854p3874.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.