Re: BinaryObjectException: Conflicting Enum Values

Hello! I guess this information was stored somewhere and is causing conflicts now. You can try dropping binary_meta/ directory from ignite work dir on all nodes, hope that it would be repopulated all right. Make sure to back it up first! Regards, -- Ilya Kasnacheev чт, 25 февр. 2021 г. в

BinaryObjectException: Conflicting Enum Values

We have recently been seeing the following error: SEVERE: Failed to serialize object [typeName=com.bloomberg.aim.wingman.cachemgr.Ts3DataCache$Ts3CalcrtKey] class org.apache.ignite.binary.BinaryObjectException: Failed to write field [name=calcrtType] at

Re: BinaryObjectException: Conflicting enum values

Hello! Currently it is not implemented. Metadata will be preserver unless cluster is restarted (in case persistence is enabled, unless it is cleared) Regards, -- Ilya Kasnacheev вс, 7 июн. 2020 г. в 02:32, Andrew Munn : > So once I insert an instance of a class in a Map I can't change the

Re: BinaryObjectException: Conflicting enum values

So once I insert an instance of a class in a Map I can't change the type of any existing member variable in the class, even if I clear the map? Seems like there should be some programatic way to clear any left-over class metadata/schema if simply clearing the cache won't do it. Right? On Sat, Jun

Re: BinaryObjectException: Conflicting enum values

You might have hit the following specificity ("Cluster Doesn’t Start After Field Type Changes") that happens if you change a type of a field: https://www.gridgain.com/docs/latest/perf-troubleshooting-guide/troubleshooting#cluster-doesnt-start-after-field-type-changes - Denis On Fri, Jun 5, 2020

BinaryObjectException: Conflicting enum values

I'm seeing the same issue as this one . I had values in the cache. I cleared the cache, but did not shutdown the cluster node. I modified the enums in the class. Then I repopulated the cache