Hi Val,
Indeed, it does make sense. Thanks for all your help.
- Luqman
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Platform-updates-tp15998p16074.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Luqman,
I meant the service deployment. Most likely, you will do this in init()
method - just call Class.forName() and create the instance of the class.
Makes sense?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Platform-updates-tp15998p16069.html
Thanks Christos, it is for the application code. For upgrading the ignite
version we can schedule the downtime that's why 99.9% :)
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Platform-updates-tp15998p16001.html
Sent from the Apache Ignite Users mailing list
Luqman, do you want to update the application or the actual Ignite version?
If it's your application Kara then as long as you can manage multiple versions
of your app for a phased upgrade then sure. But if it's for Ignite then this is
not possible to have 2 different version running in the same
