Hello!
You can implement this yourself if you really need it.
Such as, you can watch an XML file, when it changes, do
Ignition.loadSpringBin(file, bean name), and then call
ignite.getOrCreateCache() on all cache configurations found in that bean.
Regards.
--
Ilya Kasnacheev
вт, 30 июн. 2020
Ok, well modifying the configuration might not be a good solution, what
if you have multiple nodes and the configurations files no longer match,
I guess you could create a service that runs on all nodes and have that
updating the XML configuration files when you add caches, there is no
need to
Hello :)
Because If I add cache by code, the cache disappears when the node is
restarted
so I want to modify the configuration file directly.
Thank you!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi!
No, you need to restart Ignite if you change xml configuration as far as
I know.
But you can add caches after Ignite is started without any problems,
both from code and from SQL, is there any reason you cannot use one of
these methods ?
Den 2020-06-30 kl. 10:47, skrev kay:
Hello,
Is
Hello,
Is there a way to modify the configuration file after Ignite Node starts?
Should I use FTP directly to create a page to modify configuration file?
I know I can add cache in ignite run time but after restart, There is not
exist cache add in runtime.
So I need to find a way modify
