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 5ABA3187FA for ; Sun, 29 Nov 2015 08:12:38 +0000 (UTC) Received: (qmail 11484 invoked by uid 500); 29 Nov 2015 08:12:38 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 11437 invoked by uid 500); 29 Nov 2015 08:12:38 -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 11427 invoked by uid 99); 29 Nov 2015 08:12:38 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Nov 2015 08:12:38 +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 C62BB1A5B28 for ; Sun, 29 Nov 2015 08:12:37 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.174 X-Spam-Level: ** X-Spam-Status: No, score=2.174 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id eXh0Ef7Z2iYa for ; Sun, 29 Nov 2015 08:12:29 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTP id 31BFA2059E for ; Sun, 29 Nov 2015 08:12:29 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mwork.nabble.com (Postfix) with ESMTP id E0F6D2EBDF94 for ; Sun, 29 Nov 2015 00:13:37 -0800 (PST) Date: Sun, 29 Nov 2015 00:03:15 -0800 (PST) From: vkulichenko To: user@ignite.apache.org Message-ID: <1448784195201-2082.post@n6.nabble.com> In-Reply-To: <1448743141688-2078.post@n6.nabble.com> References: <1448743141688-2078.post@n6.nabble.com> Subject: Re: Cache refresh from persistent store question MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Satya, Read-through means that cache.get() operation will make an attempt to load value from the persistence store if it doesn't exist in cache. Write-through means that any cache update (put, remove, ...) will be delegated to the store. Can you please clarify what cache operations you execute and what behavior you expect? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-refresh-from-persistent-store-question-tp2078p2082.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.