Hi Val, I somehow missed the response, my bad. I'll take a look at it & get back in case I have follow up questions.
Thanks, Subru On Mon, Aug 8, 2016 at 5:10 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Subru, > > There is a response from me in the thread: http://apache-ignite- > users.70518.x6.nabble.com/Question-on-serializibility- > constraint-for-key-values-in-Ignite-JCache-td6434.html > > Please respond there if you have follow up questions. > > -Val > > On Mon, Aug 8, 2016 at 4:11 PM, Subru Krishnan <su...@apache.org> wrote: > >> Trying dev group as didn't get any response from the user group. >> >> Any pointers will be helpful. >> >> Thanks, >> Subru >> >> >> ---------- Forwarded message ---------- >> From: Subru Krishnan <su...@apache.org> >> Date: Wed, Jul 20, 2016 at 6:30 PM >> Subject: Question on serializibility constraint for key-values in Ignite >> JCache >> To: u...@ignite.apache.org >> >> >> Hi, >> >> I am working on scaling YARN through Federation (YARN-2915 >> <https://issues.apache.org/jira/browse/YARN-2915>) and as part of it was >> looking for a JCache provider for a local cache for the Federation >> StateStore. >> >> I found Ignite interesting but hit a constraint with my cache entities not >> being serializable when I tried to bootstrap an Ignite based JCache. IIUC >> JCache spec does not mandate this constraint. Moreover I tried ehcache and >> didn't hit this issue. >> >> Is there a workaround this restriction as my cache is purely local? Or is >> there an option to plugin protocol buffers as the serialization provider? >> I >> skimmed the docs/code but couldn't find a solution so I thought I'll check >> out the mailing list. >> >> Thanks, >> Subru >> > >
