When it comes to Ignite schema changes you can always update your POJOs (add or remove fields) on the application end. The cluster will see the change and will work with the new object version without any restarts. Also, if you'd like the schema changes to be visible to Ignite SQL engine you can always use ALTER TABLE/DROP INDEX/CREATE INDEX commands.
Those schema changes are not propagated to external databases Ignite can be configured to work with. You will need to adjust the tables of the external database separately. Does it make sense? Otherwise, please share more details. - Denis On Sat, May 23, 2020 at 5:16 AM manueltg89 < [email protected]> wrote: > I want to be able to change schema on runtime to my Apache Ignite app > wiithout restarting it. I've read that for this I need to use BinaryObject > on my store, but when I configure my cache store factory with "JDBC BLOB > store factory" load cache is not working, the process finished correctly > but no data on my cache. I am using "Automatic RDBMS Integration" and with > "JDBC POJO store factory" this works perfectly. I've seen this issue on > JIRA https://issues.apache.org/jira/browse/IGNITE-12078 Is there another > way to do this? Thanks in advance. > ------------------------------ > Sent from the Apache Ignite Users mailing list archive > <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com. >
