Re: Cassandra cache store [IGNITE-1371]

2016-04-07 Thread irudyak
into repository: https://github.com/irudyak/ignite 4) Current implementation is available in branch "ignite-1371" -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Cassandra-cache-store-IGNITE-1371-tp6880p8313.html Sent from the Apache Ignite Developers ma

Re: Cassandra cache store [IGNITE-1371]

2016-03-09 Thread irudyak
Hi guys, I am quite busy now. It looks like I'll just start implementing PersistenceCallback in a month. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Cassandra-cache-store-IGNITE-1371-tp6880p7827.html Sent from the Apache Ignite Developers mailing list

Re: Cassandra cache store [IGNITE-1371]

2016-02-19 Thread Denis Magda
. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Cassandra-cache-store-IGNITE-1371-tp6880p7466.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: Cassandra cache store [IGNITE-1371]

2016-02-19 Thread irudyak
Well, it just depends on how soon you are going to publish release 1.6. It will take about 1 month for me to implement PersistenceCallback. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Cassandra-cache-store-IGNITE-1371-tp6880p7466.html Sent from

Re: Cassandra cache store [IGNITE-1371]

2016-02-18 Thread Denis Magda
il.com> wrote: Actually the idea of PersistenceCallback interface looks good. I'll try to think how it's better to implement CassandraData class. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Cassandra-cache-store-IGNITE-1371-tp6880p7436.html Sent

Re: Cassandra cache store [IGNITE-1371]

2016-02-17 Thread Dmitriy Setrakyan
iew this message in context: > http://apache-ignite-developers.2346864.n4.nabble.com/Cassandra-cache-store-IGNITE-1371-tp6880p7436.html > Sent from the Apache Ignite Developers mailing list archive at Nabble.com. >

Re: Cassandra cache store [IGNITE-1371]

2016-02-17 Thread irudyak
Actually the idea of PersistenceCallback interface looks good. I'll try to think how it's better to implement CassandraData class. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Cassandra-cache-store-IGNITE-1371-tp6880p7436.html Sent from the Apache

Re: Cassandra cache store [IGNITE-1371]

2016-01-28 Thread Alexey Kuznetsov
I like Val suggestion. Also in this case we could move external things like Kryo into separate module/dependency (for those who do not want to depend on Kryo). This could be "ignite-cassandra-kryo" module that will contain smth. like "KryoPersistenceCallback". Thoughts? On Fri, Jan 29, 2016 at

Cassandra cache store [IGNITE-1371]

2016-01-28 Thread Alexey Kuznetsov
During review I faced the problem, that I have not enough experience to answer. So, it will be great, if someone who has deep experience with Binary marshaller could help us. --- > How about such limitations of Binary Marshaller: > 1) Fields or types with the same name

Re: Cassandra cache store [IGNITE-1371]

2016-01-28 Thread Valentin Kulichenko
Alexey, Igor, Binary format is internal format used by Ignite, it can't be used directly or outside of Ignite. So there is no way and no reason to have special binary serializer in Cassandra store implementation. If user wants to save BinaryObject as a BLOB to the store (to later load it back to