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 E968F17A94 for ; Mon, 2 Nov 2015 09:49:44 +0000 (UTC) Received: (qmail 67749 invoked by uid 500); 2 Nov 2015 09:49:22 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 67704 invoked by uid 500); 2 Nov 2015 09:49:22 -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 67694 invoked by uid 99); 2 Nov 2015 09:49:22 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Nov 2015 09:49:22 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 5CE9C180332 for ; Mon, 2 Nov 2015 09:49:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.973 X-Spam-Level: X-Spam-Status: No, score=0.973 tagged_above=-999 required=6.31 tests=[SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ErASaJbf3nc2 for ; Mon, 2 Nov 2015 09:49:14 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTP id E45E520864 for ; Mon, 2 Nov 2015 09:49:13 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 7ACF918FE1C7 for ; Mon, 2 Nov 2015 01:38:48 -0800 (PST) Date: Mon, 2 Nov 2015 01:40:54 -0800 (PST) From: Denis Magda To: user@ignite.apache.org Message-ID: <1446457254504-1808.post@n6.nabble.com> In-Reply-To: <1446433256745-1802.post@n6.nabble.com> References: <1445959740137-1723.post@n6.nabble.com> <1446086927236-1754.post@n6.nabble.com> <1446207082062-1778.post@n6.nabble.com> <1446212745651-1782.post@n6.nabble.com> <1446293648958-1795.post@n6.nabble.com> <1446433256745-1802.post@n6.nabble.com> Subject: Re: The result of cross-cache SQL joins is incomplete. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > There is another question, when I put table data into REPLICATED cache, This operation is synchronous or asynchronous? cache.put is synchronous. However, you can make behave him asynchronously this way: cache.withAsync().put(...) > If it is asynchronous, how can I know when this operation has finished? cache.withAsync().put(...); // blocks until the put above is finished cache.future().get(); In addition I would like to let you know that you always can change the way data is synchronized during put or other modification operations using CacheWriteSynchronizationMode that can be changed for a CacheConfiguration. Regards, Denis -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/The-result-of-cross-cache-SQL-joins-is-incomplete-tp1723p1808.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.