ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vkulichenko <valentin.kuliche...@gmail.com>
Subject Re: JDBC store Date deserialization problem
Date Fri, 18 Aug 2017 20:28:22 GMT
Hi Franck,

Can you attach your configuration and model classes if you have any? I'm
looking at the code and don't see how what you describe can happen. Date is
always written with type flag value 11.

As for store on the client, this is actually a requirement for transactional
caches which update the store from the node that runs transaction. For
atomic caches there is no such requirement, but internal mechanisms work in
the same way. You will have to deploy store implementation everywhere.


View this message in context: http://apache-ignite-users.70518.x6.nabble.com/JDBC-store-Date-deserialization-problem-tp16276p16301.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message