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 A684018EB4 for ; Fri, 1 Apr 2016 03:06:58 +0000 (UTC) Received: (qmail 39820 invoked by uid 500); 1 Apr 2016 03:06:58 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 39778 invoked by uid 500); 1 Apr 2016 03:06:58 -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 39768 invoked by uid 99); 1 Apr 2016 03:06:58 -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, 01 Apr 2016 03:06:58 +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 1D5701A0507 for ; Fri, 1 Apr 2016 03:06:58 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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 mx2-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 sypbG4aOZTxn for ; Fri, 1 Apr 2016 03:06:56 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTP id 90C725FAD9 for ; Fri, 1 Apr 2016 03:06:55 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id CE0E524359C9 for ; Thu, 31 Mar 2016 19:55:30 -0700 (PDT) Date: Thu, 31 Mar 2016 19:53:31 -0700 (PDT) From: arthi To: user@ignite.apache.org Message-ID: <1459479211489-3840.post@n6.nabble.com> In-Reply-To: References: <1459409107424-3812.post@n6.nabble.com> Subject: Re: Affinity Collocation - Using CacheKeyConfiguration - Multiple fields MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Alexey, To eloborate, I have two classes, each has a unique identifier, and also two fields - field A and field b. I join the two classes in SQL queries based on field A and field B. The two caches (of the two classes) are partitioned. I want to ensure entries with the same values of field A and field B from the caches reside in the same node to get faster SQL runs. Possible? Thanks, Arthi -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Affinity-Collocation-Using-CacheKeyConfiguration-Multiple-fields-tp3812p3840.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.