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 47F8F200CEF for ; Sun, 6 Aug 2017 07:17:53 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4647F164A5A; Sun, 6 Aug 2017 05:17:53 +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 B0611164A55 for ; Sun, 6 Aug 2017 07:17:52 +0200 (CEST) Received: (qmail 22475 invoked by uid 500); 6 Aug 2017 05:17:51 -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 22465 invoked by uid 99); 6 Aug 2017 05:17:51 -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; Sun, 06 Aug 2017 05:17:51 +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 34500C0107 for ; Sun, 6 Aug 2017 05:17:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.173 X-Spam-Level: ** X-Spam-Status: No, score=2.173 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id d-d4Q021-rWc for ; Sun, 6 Aug 2017 05:17:50 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 496215F56A for ; Sun, 6 Aug 2017 05:17:50 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mwork.nabble.com (Postfix) with ESMTP id 2BBB85985E03C for ; Sat, 5 Aug 2017 22:17:48 -0700 (MST) Date: Sat, 5 Aug 2017 22:17:48 -0700 (MST) From: iostream To: user@ignite.apache.org Message-ID: <1501996668173-16015.post@n6.nabble.com> Subject: Query about running SQL with durable memory MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Sun, 06 Aug 2017 05:17:53 -0000 Hi, I want to understand how SQL queries work when persistence store is enabled in v2.1. Suppose I have 10 Person entries in the disk, out of which only 5 are in-memory. Now if I run a SQL query which is expected to count the number of entries in Person cache, will the query run only on the disk or RAM or will it run on both? If the query will run on both the disk and RAM, will the count be 10 or 15 (10 on disk + 5 in RAM)? Does the SQL processor know which entries are present in-memory to resolve duplicates? Thanks! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Query-about-running-SQL-with-durable-memory-tp16015.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.