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 4B1DF200C01 for ; Thu, 19 Jan 2017 17:49:35 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 49C7A160B54; Thu, 19 Jan 2017 16:49:35 +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 91F42160B3A for ; Thu, 19 Jan 2017 17:49:34 +0100 (CET) Received: (qmail 11233 invoked by uid 500); 19 Jan 2017 16:49:33 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 11224 invoked by uid 99); 19 Jan 2017 16:49:33 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jan 2017 16:49:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 6795DC1C60 for ; Thu, 19 Jan 2017 16:49:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id uGw0Q7O4bblb for ; Thu, 19 Jan 2017 16:49:32 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2834A5F282 for ; Thu, 19 Jan 2017 16:49:32 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B2568E865D for ; Thu, 19 Jan 2017 16:49:28 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4FD2125289 for ; Thu, 19 Jan 2017 16:49:27 +0000 (UTC) Date: Thu, 19 Jan 2017 16:49:27 +0000 (UTC) From: "Denis Magda (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-4526) Add Spark Shared RDD examples MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 19 Jan 2017 16:49:35 -0000 [ https://issues.apache.org/jira/browse/IGNITE-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830233#comment-15830233 ] Denis Magda commented on IGNITE-4526: ------------------------------------- [~manish__mishra], don't we need to add "netty" dependency to scala-2.10 profile? I would recommend you to check that the example works with scala-2.10. Just do this locally. The profile can be switched using IntellijIdea "Maven Project"->"Profiles" tab (see attached screenshot). The rest looks good to me. > Add Spark Shared RDD examples > ----------------------------- > > Key: IGNITE-4526 > URL: https://issues.apache.org/jira/browse/IGNITE-4526 > Project: Ignite > Issue Type: Task > Reporter: Denis Magda > Assignee: Manish Mishra > Fix For: 2.0 > > Attachments: SuiteSnapShot.png > > > Spark Shared RDD functionality doesn't have its own examples. We need to add an example that will do the following: > - First Spark Worker: creation of a shared RDD and filling it in with data. > - First Spark Worker: performing some native spark transformation with the RDD. > - Second Spark Worker: connecting to the same shared RDD. > - Second Spark Worker: execution of SQL query using Spark API and Ignite API. Show that Ignite's query executes faster. > The reason why the example should consist of two workers is to showcase one of the main benefits of Ignite's RDDs - ability to share the state (RDD) amid different Spark workers and processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)