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 D3A51200C08 for ; Thu, 12 Jan 2017 06:40:51 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id D22E2160B50; Thu, 12 Jan 2017 05:40:51 +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 26383160B4E for ; Thu, 12 Jan 2017 06:40:50 +0100 (CET) Received: (qmail 15363 invoked by uid 500); 12 Jan 2017 05:40:50 -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 15353 invoked by uid 99); 12 Jan 2017 05:40:50 -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, 12 Jan 2017 05:40:50 +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 C7427C13F0 for ; Thu, 12 Jan 2017 05:40:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.424 X-Spam-Level: ** X-Spam-Status: No, score=2.424 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_ENVFROM_END_DIGIT=0.25, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] 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 Ti5w2NkMV8g2 for ; Thu, 12 Jan 2017 05:40:49 +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 90E895FDA5 for ; Thu, 12 Jan 2017 05:40:48 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id 9886B3A1B14A for ; Wed, 11 Jan 2017 21:24:06 -0800 (PST) Date: Wed, 11 Jan 2017 22:40:47 -0700 (MST) From: pragmaticbigdata To: user@ignite.apache.org Message-ID: <1484199647855-10052.post@n6.nabble.com> In-Reply-To: <1484170367858-10039.post@n6.nabble.com> References: <1484136920555-10031.post@n6.nabble.com> <1484170367858-10039.post@n6.nabble.com> Subject: Re: Re-partitioning when partition key changes MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Thu, 12 Jan 2017 05:40:52 -0000 We have a dynamic model hence we plan to use the BinaryObject API. Our cache looks like IgniteCache. Out of the number of attributes that could be part of the cache key, we plan to define the partition key through the AffinityKeyMapper interface implementation. In the affinityKey(key) method we would define the attributes whose values should be used by Ignite to partition the cache across server nodes. These attributes could change at runtime based on user input. How can we let Ignite know that the key partition has changed and it should recall the AffinityKeyMapper? What would be the locking behavior? If re-partitioning cannot be done, what are the recommended workarounds? Thanks! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Re-partitioning-when-partition-key-changes-tp10031p10052.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.