Re: Data Loss while upgrading custom jar from old jar in server and client nodes

Ivan, there are some questions related to ticket IGNITE-8162: 1. deleting a file of cache configuration leads to successfuly getting cache clonfiguration. But, is there guarantee that cache will work correctly? 2. if deleting a file of cache configuration is enough to get cache able to work,

Re: Data Loss while upgrading custom jar from old jar in server and client nodes

Thanks, Ivan, It will be good if we fix usability issues like that as soon as possible because usually, they don't involve much effort. Igniters, is anyone interested to implement the improvement for 2.5 release? -- Denis On Fri, Apr 6, 2018 at 4:12 AM, Ivan Rakov

Re: Data Loss while upgrading custom jar from old jar in server and client nodes

Denis, I'm sure we can: https://issues.apache.org/jira/browse/IGNITE-8162 Best Regards, Ivan Rakov On 05.04.2018 22:39, Denis Magda wrote: Ivan, How can we facilitate the user here? Can we generate a meaningful exception that explains how to tackle the issue? -- Denis On Thu, Apr 5, 2018

Re: Data Loss while upgrading custom jar from old jar in server and client nodes

Ivan, How can we facilitate the user here? Can we generate a meaningful exception that explains how to tackle the issue? -- Denis On Thu, Apr 5, 2018 at 2:49 AM, Ivan Rakov wrote: > Hi, > > Cache configuration is persisted in >

Re: Data Loss while upgrading custom jar from old jar in server and client nodes

Hi, Cache configuration is persisted in db\{consistent-ID}\cache-{cache-name}\cache_data.dat file. It's just CacheConfiguration serialized by JDK marshaller. Try to delete this file and start cache with new configuration (with correct factory class names). All your data will persist as long

Re: Data Loss while upgrading custom jar from old jar in server and client nodes

Ivan R., Alex G., persistence experts, Please have a look at this question. -- Denis On Mon, Apr 2, 2018 at 6:15 AM, Andrey Mashenkov wrote: > Crossposting to dev. > > Guys, > User use Ignite native persistence with CacheStore configured. > Seems, changing

Fwd: Data Loss while upgrading custom jar from old jar in server and client nodes

Crossposting to dev. Guys, User use Ignite native persistence with CacheStore configured. Seems, changing CacheStore requires cache recreation in his case to changes can be applied. Does anybody has idea how it can be fixed? Do we allow to rewrite cache config in native store if it has minor