Ignite and third party database realize data persistence real - time loading problem

classic Classic list List threaded Threaded
2 messages Options
hulitao198758 hulitao198758
Reply | Threaded
Open this post in threaded view
|

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/
ilya.kasnacheev ilya.kasnacheev
Reply | Threaded
Open this post in threaded view
|

Re: Ignite and third party database realize data persistence real - time loading problem

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 <[hidden email]>:
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/