Hello! I think that maybe you could try coding such a cache store which will update this information. It's just that the default Cassandra store doesn't seem to.
Regards, -- Ilya Kasnacheev сб, 19 дек. 2020 г. в 05:17, xmw45688 <xw...@procurant.com>: > Thanks for your confirmation, Ilya. > > I do have a follow-up question for you. > When Ignite Persistence is used together with Cassandra. The caches for > Cassandra table mappings are provided via xml file. The java class for the > mappings is for BOTH Ignite Persistence and Cassandra cache store. When a > table is changed, the mapping class gets changed, and the cluster is > started. Why is Ignite Persistence able to use this updated java class > (added/removed variables from the class) to insert/update data into Ignite > Persistence stores. But for Cassandra Store, it appears to use the old > definition of class. For this case, what's effort if we want to use the > new > class of definition? Do you think that it's reasonable to read the cache > configuration (i.e. via xml) dynamically for 3rd party Cache store which > does if the 3rd party store is used along. I'm not an expert in java, I > can > definitely help (or find a resource to do it) to improve this request. > > Pleas let me know if I can submit a feature request. > > Appreciate your help. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
