Hi!
Any chance you could do it at the "client" end ? telling the client(s)
to use another cache instead of the alias function, I guess that all
depends on how you query the data.
So create another cache, load it with the data and tell "client" to use
the other cache instead and then delete the old cache.
Another way would be messing around with the keys, load the new data
with a different "key" (some kind of version number) and switch to use
the new one when it's loaded and then delete the old.
But all of these solutions require some kind of cooperation from the
query client so I am not sure it is possible for you to do that.
Mikael
Den 2019-12-12 kl. 03:50, skrev Renato Melo:
Hello,
Periodically I need to reload a cache that is being massive queried by
a stream application.
In my current solution every reload I drop the cache, recreate it and
reload data. Caches are persisted in the file system.
I am looking for alternatives to minimize downtime when reloading caches.
What alternatives does ignite offer?
Some relational databases offer CREATE TABLE ALIAS option. Using an
alias I would be able to create a new table, reload data and when
ready, pointing the alias to the new table having minimum downtime.
I read ignited does not allow cache renaming neither offers support
for "CREATE ALIAS".
What alternatives do you suggest?
Best regards,
Renato de Melo
