You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by hulitao198758 <hu...@lenovo.com> on 2019/02/22 07:44:26 UTC
Ignite and third party database realize data persistence real -
time loading problem
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/
Re: Ignite and third party database realize data persistence real -
time loading problem
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
When you do SQL queries on Ignite caches with 3rd party persistence, data
will not be pulled from underlying DB. You will only be querying what's in
the cache currently.
Consider using loadCache() to fully load data before doing queries.
Regards,
--
Ilya Kasnacheev
пт, 22 февр. 2019 г. в 10:44, hulitao198758 <hu...@lenovo.com>:
> 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/
>