Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 32E2418002 for ; Thu, 18 Feb 2016 19:19:48 +0000 (UTC) Received: (qmail 56434 invoked by uid 500); 18 Feb 2016 19:19:25 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 56393 invoked by uid 500); 18 Feb 2016 19:19:25 -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 56383 invoked by uid 99); 18 Feb 2016 19:19:25 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Feb 2016 19:19:25 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 7BD65C00ED for ; Thu, 18 Feb 2016 19:19:25 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id NEuK6x1Wpzh3 for ; Thu, 18 Feb 2016 19:19:24 +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 1A46D5FAEB for ; Thu, 18 Feb 2016 19:19:24 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id ED7A4210AE2C for ; Thu, 18 Feb 2016 11:12:35 -0800 (PST) Date: Thu, 18 Feb 2016 11:07:25 -0800 (PST) From: vkulichenko To: user@ignite.apache.org Message-ID: <1455822445502-3087.post@n6.nabble.com> In-Reply-To: <1455797769468-3084.post@n6.nabble.com> References: <1455766376807-3071.post@n6.nabble.com> <1455778366670-3073.post@n6.nabble.com> <1455797769468-3084.post@n6.nabble.com> Subject: Re: Pagination to fetch complete Cache data MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Fetching all entries to the client will never be effective because it involves transferring too much data across network. If you need to process the whole data set, it's usually better to use Compute Grid [1]. Broadcast a closure or execute a map-reduce task and send only results to the client. Is it something that can work for you? NPE in SQL is a known issue and already fixed. You can build Ignite from master and check if it works for you. [1] https://apacheignite.readme.io/docs/compute-grid -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Pagination-to-fetch-complete-Cache-data-tp3071p3087.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.