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 8873017A4F for ; Sat, 9 Jan 2016 18:13:40 +0000 (UTC) Received: (qmail 58353 invoked by uid 500); 9 Jan 2016 18:13:40 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 58308 invoked by uid 500); 9 Jan 2016 18:13:40 -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 58298 invoked by uid 99); 9 Jan 2016 18:13:40 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Jan 2016 18:13:40 +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 CA7C51A048C for ; Sat, 9 Jan 2016 18:13:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.174 X-Spam-Level: ** X-Spam-Status: No, score=2.174 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id LVvOOLQcuN-8 for ; Sat, 9 Jan 2016 18:13:30 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTP id CC7F525E93 for ; Sat, 9 Jan 2016 18:13:29 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 982E31DCD99C for ; Sat, 9 Jan 2016 10:11:02 -0800 (PST) Date: Sat, 9 Jan 2016 10:02:51 -0800 (PST) From: vinshar To: user@ignite.apache.org Message-ID: <1452362571917-2464.post@n6.nabble.com> Subject: Cross Cache Affinity MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I went through documentation for enabling Affinity at below link https://apacheignite.readme.io/docs/affinity-collocation Following are my queries:- 1) Document has an example where same cache is used to hold different type of cache objects. Is this advisable and is this necessary to achieve collocation of objects? 2) Is there any case where it may make sense to use Affinity Key's in case of a replicated cache? 3) For cross cache SQL Queries, Cached objects should be collocated. If this is correct then how can i achieve this? Regards, Vinay Sharma -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cross-Cache-Affinity-tp2464.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.