From user-return-17524-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Jan 29 11:04:17 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 8DA98180654 for ; Mon, 29 Jan 2018 11:04:17 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 7E1CE160C3F; Mon, 29 Jan 2018 10:04:17 +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 EBAA0160C31 for ; Mon, 29 Jan 2018 11:04:16 +0100 (CET) Received: (qmail 18587 invoked by uid 500); 29 Jan 2018 10:04:15 -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 18577 invoked by uid 99); 29 Jan 2018 10:04:15 -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; Mon, 29 Jan 2018 10:04:15 +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 6EECD1A299C for ; Mon, 29 Jan 2018 10:04:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.172 X-Spam-Level: ** X-Spam-Status: No, score=2.172 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id IzouzVmnAb1X for ; Mon, 29 Jan 2018 10:04:11 +0000 (UTC) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D8A7D5F23D for ; Mon, 29 Jan 2018 10:04:10 +0000 (UTC) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 6EE2E43EA623 for ; Mon, 29 Jan 2018 03:04:10 -0700 (MST) Date: Mon, 29 Jan 2018 03:04:10 -0700 (MST) From: "ilya.kasnacheev" To: user@ignite.apache.org Message-ID: <1517220250451-0.post@n6.nabble.com> In-Reply-To: References: Subject: Re: cache configuration without Key MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Rajesh! In Ignite, cache (and SQL table) maps not to one object but to two - key and value. Keys are unique per cache per cluster. They act as primary key in SQL and as, well, keys in cache API. So yes, you need to specify key type (or compound object) too. Regards, Ilya. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/