Hi Val, Thanks for the info. I replied to both questions.
Regarding the first question - we just don't support mapping from java.sql.Timestamp to Cassandra's Datatype.Name.TIMESTAMP type, cause there are no direct mapping for it http://docs.datastax.com/en/developer/java-driver/3.1/manual/#cql-to-java-type-mapping. We can easily add support for this mapping, but there actually plenty of other Timestamp types in core java (java.sql.Timestamp, java.security.Timestamp, java.sun.jmx.snmp.Timestamp and etc.) and even more in different third party libraries. Thus it's just technically not possible to add support for all variety of Timestamps. Regarding second question - in current implementation, complex data types (collections, custom types) could only be mapped to BLOB type in Cassandra. Igor On Thu, Mar 30, 2017 at 5:39 PM, Valentin Kulichenko < [email protected]> wrote: > Hi Igor, > > There are two recent questions on the user forum regarding > ignite-cassandra module, and they seem to be very similar to each other: > > - http://apache-ignite-users.70518.x6.nabble.com/Timestamp- > is-not-stored-correctly-with-Cassandra-td11590.html > > <http://apache-ignite-users.70518.x6.nabble.com/Timestamp-is-not-stored-correctly-with-Cassandra-td11590.html> > - http://apache-ignite-users.70518.x6.nabble.com/Mapping- > java-util-Map-in-CassandraPersistentStore-td11574.html > > <http://apache-ignite-users.70518.x6.nabble.com/Mapping-java-util-Map-in-CassandraPersistentStore-td11574.html> > > Can you please take a look? > > Do we support all Cassandra data types properly? If not, why? > > -Val >
