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 DB75B200C3C for ; Mon, 3 Apr 2017 19:40:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D85F2160B8F; Mon, 3 Apr 2017 17:40:25 +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 2BD38160B8D for ; Mon, 3 Apr 2017 19:40:25 +0200 (CEST) Received: (qmail 34340 invoked by uid 500); 3 Apr 2017 17:40:24 -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 34331 invoked by uid 99); 3 Apr 2017 17:40:24 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Apr 2017 17:40:24 +0000 Received: from mail-yb0-f173.google.com (mail-yb0-f173.google.com [209.85.213.173]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 06AD91A00E8 for ; Mon, 3 Apr 2017 17:40:24 +0000 (UTC) Received: by mail-yb0-f173.google.com with SMTP id i124so38968205ybc.3 for ; Mon, 03 Apr 2017 10:40:23 -0700 (PDT) X-Gm-Message-State: AFeK/H2+5OowrWCjnqfxtdFSAEvZDcxCKvohGXtfvMJOS3HETWm6aEfXwN/YEKNRLHs9ZKSNeUIh9E4P2bxtcQ== X-Received: by 10.37.161.2 with SMTP id z2mr11744513ybh.50.1491241223099; Mon, 03 Apr 2017 10:40:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.178.135 with HTTP; Mon, 3 Apr 2017 10:40:22 -0700 (PDT) In-Reply-To: <1491235438704-11670.post@n6.nabble.com> References: <1490974155010-11627.post@n6.nabble.com> <1491003795432-11634.post@n6.nabble.com> <1491007759047-11636.post@n6.nabble.com> <1491235438704-11670.post@n6.nabble.com> From: Andrey Gura Date: Mon, 3 Apr 2017 20:40:22 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Client near cache with Apache Flink To: user@ignite.apache.org Content-Type: text/plain; charset=UTF-8 archived-at: Mon, 03 Apr 2017 17:40:26 -0000 What is the source of your data in case *without* Ignite cache? I'm trying to understand your design without Ignite. What does your code instead of nearCache.get(key)? Also the code snippet that creates code still should fail because it try to create near cache for original cache that doesn't exist yet. On Mon, Apr 3, 2017 at 7:03 PM, nragon wrote: > Hi, > > The code is not all there but i think it's the important one. > Cache access: this.nearCache.get(key); (Mentioned above) > Cache name comes from table.getName() which, for instance, can be > "LK_SUBS_UPP_INST". > Data in ignite cache: String key and Object[] value. For now I only have one > record for each cache (3 total) > +======================================================================================================================+ > | Key Class | Key | Value Class | > Value | > +======================================================================================================================+ > | java.lang.String | 1 | java.lang.Object[] | size=10, values=[1, 1, null, > null, null, null, null, null, null, null] | > +----------------------------------------------------------------------------------------------------------------------+ > > The cache is loaded with datastreamer from oracle database. Again, loading > is not the problem. > I'm trying to understand if this (this.nearCache.get(key)) is the best way > to access for fast lookups. > > Thanks > > > > > -- > View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Client-near-cache-with-Apache-Flink-tp11627p11670.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.