Re: use java code to dynamic change sturcture of cache value
Basically you need to do both: change the Java class and run the SQL “ALTER TABLE” command. Until Ignite 3.0, they are (effectively) two distinct schemas, and you need to manage them separately. > On 19 Aug 2021, at 11:14, 常鑫 wrote: > > > Hi All, >We are using Ignite 2.10.0 and we have a question on dynamic change > sturcture of cache value. > For example, a cache stores objects of the Person type.At first,it have > two field: "name" and "salary",then a new node join the cluster ,but the > person type it used have three field:"name"、 “salary" and "newCol". I can > operate the new field with key-value API.But I can't see it from SQL > Tools.The SQL tool shows columns only which are present when Ignite cache has > been initialized first time. >So how to publish the java code structure to the table structure.I know > the ddl language,but I still wonder the answer. > > > - > Thanks & Regards, > Xin Chang > >
use java code to dynamic change sturcture of cache value
Hi All, We are using Ignite 2.10.0 and we have a question on dynamic change sturcture of cache value. For example, a cache stores objects of the Person type.At first,it have two field: "name" and "salary",then a new node join the cluster ,but the person type it used have three field:"name"、 “salary" and "newCol". I can operate the new field with key-value API.But I can't see it from SQL Tools.The SQL tool shows columns only which are present when Ignite cache has been initialized first time. So how to publish the java code structure to the table structure.I know the ddl language,but I still wonder the answer. - Thanks & Regards, Xin Chang
Re: BinaryObjectException: Unsupported protocol version
Hello, Most probably it's related to [1], which is fixed since Ignite 2.9.1. [1]: https://issues.apache.org/jira/browse/IGNITE-13401 чт, 19 авг. 2021 г. в 09:53, Naveen Kumar : > Hi All > > We are using Ignite 2.8.1 and using the thin clients majorly. > Facing a strange issues for last couple of days, all PUTs are working > fine, but GETs are failing with a reason : BinaryObjectException: > Unsupported protocol version. > > After the node restart, GETs started working fine, and dont see anything > specific in the node logs as well. > > Any pointers towards this, how did the node restart resolved the issue. > > None of the GETs were working earlier only PUTs were working (PUTs were > done thru JDBC SQL), GERs are using the Java KV API. > > -- > Thanks & Regards, > Naveen Bandaru >
BinaryObjectException: Unsupported protocol version
Hi All We are using Ignite 2.8.1 and using the thin clients majorly. Facing a strange issues for last couple of days, all PUTs are working fine, but GETs are failing with a reason : BinaryObjectException: Unsupported protocol version. After the node restart, GETs started working fine, and dont see anything specific in the node logs as well. Any pointers towards this, how did the node restart resolved the issue. None of the GETs were working earlier only PUTs were working (PUTs were done thru JDBC SQL), GERs are using the Java KV API. -- Thanks & Regards, Naveen Bandaru
