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 E5B7D200BEF for ; Wed, 4 Jan 2017 13:03:41 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E480C160B3A; Wed, 4 Jan 2017 12:03:41 +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 3AFCB160B39 for ; Wed, 4 Jan 2017 13:03:41 +0100 (CET) Received: (qmail 43788 invoked by uid 500); 4 Jan 2017 12:03:35 -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 43776 invoked by uid 99); 4 Jan 2017 12:03:35 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2017 12:03:35 +0000 Received: from mail-it0-f47.google.com (mail-it0-f47.google.com [209.85.214.47]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 1EE871A058E for ; Wed, 4 Jan 2017 12:03:35 +0000 (UTC) Received: by mail-it0-f47.google.com with SMTP id o141so298301502itc.0 for ; Wed, 04 Jan 2017 04:03:35 -0800 (PST) X-Gm-Message-State: AIkVDXJUhq5P932xjFXBT1r1pxy+s6yfCRT3MnOEnf/cVBs3SuH2jXr53ZrD3Q4b8F6Mr/DwMVzk3f2fM9Zyxjad X-Received: by 10.36.137.84 with SMTP id s81mr47682329itd.117.1483531414597; Wed, 04 Jan 2017 04:03:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.155.86 with HTTP; Wed, 4 Jan 2017 04:03:34 -0800 (PST) In-Reply-To: <1483530213934-9865.post@n6.nabble.com> References: <1483518717325-9859.post@n6.nabble.com> <1483530213934-9865.post@n6.nabble.com> From: Nikolai Tikhonov Date: Wed, 4 Jan 2017 15:03:34 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: NearCache can be used through ODBC interface To: user@ignite.apache.org Content-Type: multipart/alternative; boundary=94eb2c05b8f4fb3a6605454392ca archived-at: Wed, 04 Jan 2017 12:03:42 -0000 --94eb2c05b8f4fb3a6605454392ca Content-Type: text/plain; charset=UTF-8 SQL query distributed on whole cluster, near cache not needed for it. Records will be read on data node (usually cache, not near) in any case for queries and usage data from near cache will not provide performance benefit. On Wed, Jan 4, 2017 at 2:43 PM, Navneet Kumar wrote: > In that case I cannot read the records from near cache using the Near > cache. > Is it true? > > > > -- > View this message in context: http://apache-ignite-users.705 > 18.x6.nabble.com/NearCache-can-be-used-through-ODBC-interfac > e-tp9859p9865.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > --94eb2c05b8f4fb3a6605454392ca Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
SQL query distributed on whole cluster, near cache not nee= ded for it. Records will be read on data node (usually cache, not near) in = any case for queries and usage data from near cache will not provide perfor= mance benefit.

On = Wed, Jan 4, 2017 at 2:43 PM, Navneet Kumar <navneetkumar.india@= gmail.com> wrote:
In that case I cannot read the records from near cache using the= Near cache.
Is it true?



--
View this message in context: http://apache-ignite-users.70518= .x6.nabble.com/NearCache-can-be-used-through-ODBC-interface-tp985= 9p9865.html
Sent from the Apache Ignite Users mailing li= st archive at Nabble.com.

--94eb2c05b8f4fb3a6605454392ca--