GitHub user irudyak opened a pull request: https://github.com/apache/ignite/pull/1111
IGNITE 3609 Utilize Cassandra logged batches for transactions You can merge this pull request into a Git repository by running: $ git pull https://github.com/irudyak/ignite ignite-3609 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1111.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1111 ---- commit 65b60d8bd7c9e341bc430ea698ba306fd54790eb Author: Igor <irud...@gmail.com> Date: 2016-09-21T21:16:51Z Utilise Cassandra logged batches to apply changes performed withing Ignite transaction commit 33e66a6e384eec9dfa3f6e276bcdcf606d258a31 Author: Igor <irud...@gmail.com> Date: 2016-09-21T21:33:34Z As far as Ignite indexes and Cassandra secondary indexes are two rather different concept it's better not to create Cassandra secondary indexes automatically for all Ignite cache indexed fields. The fields for which Cassandra secondary indexes should be created should be specified explicitly in persistence descriptor xml file. commit c8c008aa120bc4fc9485b9130796eac0ed5c191a Author: Igor <irud...@gmail.com> Date: 2016-09-21T21:42:38Z minor bugfix in handling @QuerySqlField annotation commit c972f25dcb91fbd6438ecec9b3c3205d6e674b3d Author: Igor <irud...@gmail.com> Date: 2016-09-22T06:21:07Z unit tests for transactional caches directly persisting changes into Cassandra bypassing Ignite commit c22b56ef8ee7b4a32f5d15dbb2ceb3c07fb9cf10 Author: Igor <irud...@gmail.com> Date: 2016-09-22T21:18:35Z minor refactoring commit 58a3053a285e332d7da94f47be36f09c3c9b36ad Author: Igor <irud...@gmail.com> Date: 2016-09-22T21:18:47Z bugfix commit 9a664f3f3863b5b9e087aa9ba609c62ef6da77ee Author: Igor <irud...@gmail.com> Date: 2016-09-22T22:10:42Z minor refactoring commit bfa4930f6dbb1cae4c5e7e04aa86f00231cb80a2 Author: Igor <irud...@gmail.com> Date: 2016-09-23T05:36:35Z unit tests for POJO objects stored inside TRANSACTIONAL caches commit edeef0ab116a52d0bc3b6034180bee2267a06a05 Author: Igor <irud...@gmail.com> Date: 2016-09-23T05:40:06Z minor refactoring commit c37ade7947137f611c51ef7e2ddd8a34bde31ad7 Author: Igor <irud...@gmail.com> Date: 2016-09-23T16:48:54Z minor refactoring commit a0b180c29daafc342a5aeef724b16719236f9812 Author: Igor <irud...@gmail.com> Date: 2016-09-23T17:01:35Z minor refactoring commit f3594b8fdd975e9e22c45a768f35994ef6f7127b Author: Igor <irud...@gmail.com> Date: 2016-09-23T21:51:52Z unit tests for Ignite transactional caches commit 2f5d90feb24461904f308a945c4fe945add28405 Author: Igor <irud...@gmail.com> Date: 2016-09-24T00:20:04Z additional verification for Cassandra logged batches commit 236a86f2147642e23ad3da6883ebf998f88a29b9 Author: Igor <irud...@gmail.com> Date: 2016-09-24T00:46:31Z simple Cassandra server sample running on localhost ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---