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 462D6200C17 for ; Fri, 27 Jan 2017 02:13:59 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 44B42160B50; Fri, 27 Jan 2017 01:13:59 +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 8DFB5160B4C for ; Fri, 27 Jan 2017 02:13:58 +0100 (CET) Received: (qmail 3212 invoked by uid 500); 27 Jan 2017 01:13:57 -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 3202 invoked by uid 99); 27 Jan 2017 01:13:57 -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; Fri, 27 Jan 2017 01:13:57 +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 50DD41A003F for ; Fri, 27 Jan 2017 01:13:57 +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 2dxRVeLUT9jS for ; Fri, 27 Jan 2017 01:13:54 +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 6EC745F472 for ; Fri, 27 Jan 2017 01:13:53 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id 5F5C63B58AD6 for ; Thu, 26 Jan 2017 16:55:24 -0800 (PST) Date: Thu, 26 Jan 2017 18:13:51 -0700 (MST) From: vkulichenko To: user@ignite.apache.org Message-ID: <1485479631790-10274.post@n6.nabble.com> In-Reply-To: <1485472603553-10273.post@n6.nabble.com> References: <1485454904778-10264.post@n6.nabble.com> <1485472603553-10273.post@n6.nabble.com> Subject: Re: Newbie: Questions on Ignite over cassandra MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Fri, 27 Jan 2017 01:13:59 -0000 I meant that Cassandra itself will be involved only when you load the data into caches, which is a separate step that should happen prior to query execution. When Ignite query is executed, Cassandra is not touched. The answer on your question is yes - any joins are possible, similar to any relational database. However, for good performance you should consider collocation and indexing. See the documentation for details: https://apacheignite.readme.io/docs/sql-grid -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Newbie-Questions-on-Ignite-over-cassandra-tp10264p10274.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.