Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 551B7200B3E for ; Wed, 7 Sep 2016 17:59:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 53A9D160ABF; Wed, 7 Sep 2016 15:59:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C13B1160ACF for ; Wed, 7 Sep 2016 17:59:21 +0200 (CEST) Received: (qmail 58362 invoked by uid 500); 7 Sep 2016 15:59:15 -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 58348 invoked by uid 99); 7 Sep 2016 15:59:15 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Sep 2016 15:59:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 851751A0658 for ; Wed, 7 Sep 2016 15:59:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.173 X-Spam-Level: ** X-Spam-Status: No, score=2.173 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, 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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id JhgT-2WhZ8W9 for ; Wed, 7 Sep 2016 15:59:13 +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 1E0A45FAD5 for ; Wed, 7 Sep 2016 15:59:13 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 7674C309F114 for ; Wed, 7 Sep 2016 08:57:33 -0700 (PDT) Date: Wed, 7 Sep 2016 08:59:11 -0700 (PDT) From: vkulichenko To: user@ignite.apache.org Message-ID: <1473263951520-7589.post@n6.nabble.com> In-Reply-To: References: Subject: Re: IgniteConfiguration object not serializable during spark job MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Wed, 07 Sep 2016 15:59:22 -0000 Hi Ming, Yes, IgniteConfiguration is indeed not serializable. That's why IgniteContext accepts factory closure to create it instead of the instance itself. You should create IgniteConfiguration inside the closure, this way it will be created on the executor and will never be serialized. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/IgniteConfiguration-object-not-serializable-during-spark-job-tp7579p7589.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.