From user-return-24906-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Feb 22 07:44:33 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id E7C47180648 for ; Fri, 22 Feb 2019 08:44:32 +0100 (CET) Received: (qmail 8284 invoked by uid 500); 22 Feb 2019 07:44:31 -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 8274 invoked by uid 99); 22 Feb 2019 07:44:31 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Feb 2019 07:44:31 +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 08A86182710 for ; Fri, 22 Feb 2019 07:44:31 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.972 X-Spam-Level: X-Spam-Status: No, score=0.972 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id VAjikSBFq0xI for ; Fri, 22 Feb 2019 07:44:27 +0000 (UTC) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4401E5F19C for ; Fri, 22 Feb 2019 07:44:27 +0000 (UTC) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 948ADC7C190C for ; Fri, 22 Feb 2019 00:44:26 -0700 (MST) Date: Fri, 22 Feb 2019 00:44:26 -0700 (MST) From: hulitao198758 To: user@ignite.apache.org Message-ID: <1550821466606-0.post@n6.nabble.com> Subject: Ignite and third party database realize data persistence real - time loading problem MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit If don't open the persistence in Ignite server startup, as in-memory database to use, can achieve using the Sql query data, if not in the memory, automatically pulled from the mysql database and loaded into memory, there is a new data to the automatic synchronization to mysql, or Ignite in future versions of this function is to develop? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/