Re: Some problems when using Ignite
Hello! BinaryObject should be solving your issues. Can you please show how the problem manifets if you don't restart cluster? Regards, -- Ilya Kasnacheev 2018-08-14 13:54 GMT+03:00 zym周煜敏 : > Hi, > > > > Our company is now on a trial survey on Ignite. We found that if we want > to alter the table schema or add a new table or even add an index when we > use the Ignite SQL, we should change our code of the data injection, > compile again, and then restart our ignite cluster to validate all the > changes. We have tried BinaryObject, but it still needs pre-setting of the > table schema and cluster restart. Are there any workarounds since it’s > expensive to restart an industial cluster which may cause data loss? If > not, will the latter version of Ignite support the dynamic changing of the > table schema? > > > > Best Regards, > > Brian Zhou > > [image: new logo] > > >
Re: Some problems when using Ignite
Hi, Dynamic schema chages is available only via SQL/JDBC [1]. BTW caches created via SQL could be accessed from java API if you add SQL_PUBLIC_ to table. For example: ignite.cache(SQL_PUBLIC_TABLENAME). [1] https://apacheignite-sql.readme.io/docs/ddl Thanks! -Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Some problems when using Ignite
Hi, Our company is now on a trial survey on Ignite. We found that if we want to alter the table schema or add a new table or even add an index when we use the Ignite SQL, we should change our code of the data injection, compile again, and then restart our ignite cluster to validate all the changes. We have tried BinaryObject, but it still needs pre-setting of the table schema and cluster restart. Are there any workarounds since it’s expensive to restart an industial cluster which may cause data loss? If not, will the latter version of Ignite support the dynamic changing of the table schema? Best Regards, Brian Zhou [new logo]
