Thank you for the reply. The client uses JDBC Driver to get the data from Ignite.
The swap between new cache and old cache should be hidden from the client. Would it be possible to do this in Ignite? My first idea is to create a new cache and fill it with new data data. Afterwards, within a transaction, the old cache content will be deleted and all the content from new cache will be inserted to the old cache. > Am 28.11.2015 um 03:35 schrieb Dmitriy Setrakyan <dsetrak...@apache.org>: > > Hi Fsapei, > > Ignite supports dynamic caches, so you can create and destroy caches on the > fly: > https://apacheignite.readme.io/docs/data-grid#section-jcache > <https://apacheignite.readme.io/docs/data-grid#section-jcache> > > To support your use case, you can: > > 1. create a new cache and start populating it > 2. while the new cache is populated, the queries should go to the old cache. > 3. when new cache is fully populated, route the queries to the new cache > 4. delete the old cache > > Will this work? > > D. > > On Sat, Nov 28, 2015 at 3:38 AM, Ferry Syafei Sapei > <ferry.sa...@googlemail.com <mailto:ferry.sa...@googlemail.com>> wrote: > Hallo, > > I would like to use Ignite as Data Grid. The cache will be initially loaded > with a lot of data (e.g. a CSV file with a size more than 10 GB). > > When a new CSV file is available, the current Cache content must be replaced > with the new data from the new CSV. The old cache content must be completely > deleted. > > The switch from old cache content to the new one must happen without > downtime. When any SQL Clients execute query during the switch, they should > still obtain any data from the old cache content, since the switch has not > finished yet. > > Could somebody please advise me, how to continuously update the cache like > the description above? > > Thank you. > > > Best regards, > fsapei > > > > >
