[GitHub] ignite pull request #3940: IGNITE-8354 Ignite Continuosly refreshes Cassandr...

[irudyak]

Github user irudyak closed the pull request at:

https://github.com/apache/ignite/pull/3940


---

[GitHub] ignite pull request #3940: IGNITE-8354 Ignite Continuosly refreshes Cassandr...

[irudyak]

GitHub user irudyak opened a pull request:

https://github.com/apache/ignite/pull/3940

IGNITE-8354 Ignite Continuosly refreshes Cassandra Session when there is an 
Exception in execute method of CassandraSessionImpl



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/irudyak/ignite ignite-8354

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3940.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 #3940


commit 2def238b89e155b163f5c61d3f84ff195dbe390c
Author: Igor Rudyak <igor.rudyak@...>
Date:   2018-04-28T23:19:25Z

IGNITE-8354




---

[GitHub] ignite pull request #3471: IGNITE-5779 Incorrect mapping of smallint cassand...

[irudyak]

GitHub user irudyak opened a pull request:

https://github.com/apache/ignite/pull/3471

IGNITE-5779 Incorrect mapping of smallint cassandra type.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/irudyak/ignite ignite-5779

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3471.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 #3471


commit fdbfb67b47659b17755b2e3c1086446d6f351ec9
Author: Igor Rudyak <igor.rudyak@...>
Date:   2018-02-05T05:55:12Z

IGNITE-5779




---

[GitHub] ignite pull request #2074: IGNITE 5368 Cassandra store should support privat...

[irudyak]

Github user irudyak closed the pull request at:

https://github.com/apache/ignite/pull/2074


---
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.
---

Re: How to store Binary Object in Cassandra Backup Store

[irudyak]

You are using invalid persistence descriptor. It should be something like:

*


*

You can find more details about persistence descriptor configuration here: 
https://apacheignite-mix.readme.io/docs/base-concepts#section-persistencesettingsbean

  



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/How-to-store-Binary-Object-in-Cassandra-Backup-Store-tp17827p17843.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[GitHub] ignite pull request #1274: IGNITE-4205 CassandraCacheStore should start Igni...

[irudyak]

GitHub user irudyak opened a pull request:

https://github.com/apache/ignite/pull/1274

IGNITE-4205 CassandraCacheStore should start IgniteThread threads in 
loadCache() method



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/irudyak/ignite ignite-4205

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1274.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 #1274


commit 9940e5e6304ffbae317209ce496f235994cf34be
Author: Igor <irud...@gmail.com>
Date:   2016-11-24T05:41:09Z

utilysing  IgniteThreadFactory for ThreadPool created inside loadCache




---
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.
---

[GitHub] ignite pull request #1189: IGNITE-4075 Cassandra store should load all avail...

[irudyak]

GitHub user irudyak opened a pull request:

https://github.com/apache/ignite/pull/1189

IGNITE-4075 Cassandra store should load all available data when no 
parameters are provided in loadCache()



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/irudyak/ignite ignite-4075

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1189.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 #1189


commit 065516322b3f568d5b9b8ad18f20053c654b5e8c
Author: Igor <irud...@gmail.com>
Date:   2016-10-27T04:46:04Z

implementation for IGNITE-4075




---
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.
---

[GitHub] ignite pull request #1111: IGNITE 3609 Utilize Cassandra logged batches for ...

[irudyak]

GitHub user irudyak opened a pull request:

https://github.com/apache/ignite/pull/

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/.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 #


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.
---

[GitHub] ignite pull request #1086: IGNITE-3313 Make table name optional in Cassandra...

[irudyak]

GitHub user irudyak opened a pull request:

https://github.com/apache/ignite/pull/1086

IGNITE-3313 Make table name optional in Cassandra persistence descriptor



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/irudyak/ignite ignite-3313

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1086.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 #1086


commit e328234cd86f2c1ca16885cdc0e20cc6d492ce85
Author: Igor <irud...@gmail.com>
Date:   2016-09-20T04:57:02Z

table name is optional now in Cassandra persistence descriptor




---
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.
---

[GitHub] ignite pull request #1062: IGNITE 3791 Wrap keyspace, table and column name ...

[irudyak]

Github user irudyak closed the pull request at:

https://github.com/apache/ignite/pull/1062


---
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.
---

[GitHub] ignite pull request #1062: Ignite 3791 Wrap keyspace, table and column name ...

[irudyak]

GitHub user irudyak opened a pull request:

https://github.com/apache/ignite/pull/1062

Ignite 3791 Wrap keyspace, table and column name with escape characters in 
generated CQL queries



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/irudyak/ignite ignite-3791

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1062.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 #1062


commit f38a14defd0f1ebd41e0f49ef19f44902d1780d0
Author: Igor <irud...@gmail.com>
Date:   2016-09-14T23:01:11Z

printing index DDL statements if there are any indexes registered for a 
table

commit 27e551fe10a9577d63ebb9e6849aba1de1e5def3
Author: Igor <irud...@gmail.com>
Date:   2016-09-14T23:02:22Z

wrapped table name, keyspace name and column names with double quotes in 
all generated DDL/DML statements




---
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.
---

[GitHub] ignite pull request #961: IGNITE-3701 Ignite Maven project version number

[irudyak]

GitHub user irudyak reopened a pull request:

https://github.com/apache/ignite/pull/961

IGNITE-3701 Ignite Maven project version number



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/irudyak/ignite ignite-3701

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/961.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 #961


commit 90af6ebc3b71add0326a52a8b426febd0441f45f
Author: Igor <irud...@gmail.com>
Date:   2016-08-17T01:26:47Z

IGNITE-3172




---
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.
---

[GitHub] ignite pull request #961: IGNITE-3701 Ignite Maven project version number

[irudyak]

Github user irudyak closed the pull request at:

https://github.com/apache/ignite/pull/961


---
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.
---

[GitHub] ignite pull request #961: IGNITE-3172 Ignite Maven project version number

[irudyak]

GitHub user irudyak opened a pull request:

https://github.com/apache/ignite/pull/961

IGNITE-3172 Ignite Maven project version number



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/irudyak/ignite ignite-3701

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/961.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 #961


commit 90af6ebc3b71add0326a52a8b426febd0441f45f
Author: Igor <irud...@gmail.com>
Date:   2016-08-17T01:26:47Z

IGNITE-3172




---
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.
---

[GitHub] ignite pull request #851: IGNITE-3417 Cassandra packages have no description...

[irudyak]

GitHub user irudyak opened a pull request:

https://github.com/apache/ignite/pull/851

IGNITE-3417 Cassandra packages have no descriptions



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/irudyak/ignite ignite-3417

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/851.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 #851


commit e09eacc745bdba4fca34f23f8589faa1b51afd86
Author: Igor <irud...@gmail.com>
Date:   2016-07-05T03:19:11Z

added javadocs for Cassandra packages




---
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.
---

[GitHub] ignite pull request #789: Fix for ignite-3293

[irudyak]

GitHub user irudyak reopened a pull request:

https://github.com/apache/ignite/pull/789

Fix for ignite-3293

It's a patch to scripts bootstrapping Ignite-Cassandra-LoadTests 
infrastructure in Amazon

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/irudyak/ignite ignite-3293

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/789.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 #789


commit a725b5f16d9b6fb4363432710cb87d420b2c8a88
Author: Igor <irud...@gmail.com>
Date:   2016-06-10T00:03:09Z

fix for ignite-3293

commit 7ba18f937fcd4d54ba156397d893731588a04f4e
Author: Igor <irud...@gmail.com>
Date:   2016-06-10T04:04:21Z

shell scripts to recreate Cassandra artifacts on each load tests execution




---
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.
---

[GitHub] ignite pull request #789: Fix for ignite-3293

[irudyak]

Github user irudyak closed the pull request at:

https://github.com/apache/ignite/pull/789


---
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.
---

[GitHub] ignite pull request #789: Fix for ignite-3293

[irudyak]

GitHub user irudyak opened a pull request:

https://github.com/apache/ignite/pull/789

Fix for ignite-3293

It's a patch to scripts bootstrapping Ignite-Cassandra-LoadTests 
infrastructure in Amazon

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/irudyak/ignite ignite-3293

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/789.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 #789


commit a725b5f16d9b6fb4363432710cb87d420b2c8a88
Author: Igor <irud...@gmail.com>
Date:   2016-06-10T00:03:09Z

fix for ignite-3293




---
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.
---

Re: Cassandra cache store [IGNITE-1371]

[irudyak]

Hi guys,

Just a short update for Cassandra persistent store implementation:

1) We switched to the newest version of Cassandra 3.3
2) Unit tests now using embedded Cassandra starting in the same process with
Ignite cluster. 
3) All the latest changes from Ignite 1.6 upstream were merged 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 mailing list archive at Nabble.com.

Re: Cassandra cache store [IGNITE-1371]

[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 archive at Nabble.com.

Re: Cassandra cache store [IGNITE-1371]

[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 the Apache Ignite Developers mailing list archive at Nabble.com.

Re: Cassandra cache store [IGNITE-1371]

[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 Ignite Developers mailing list archive at Nabble.com.

[GitHub] ignite pull request: IGNITE-1371 implemented

[irudyak]

GitHub user irudyak opened a pull request:

https://github.com/apache/ignite/pull/172

IGNITE-1371 implemented



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/irudyak/ignite ignite-1371

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/172.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 #172


commit 3b5c293894446a3013804e8a475d4a687e8b56f3
Author: Igor <irud...@gmail.com>
Date:   2015-10-16T05:39:26Z

ignite 1371: Implemented.

commit a89daea495a32a7bd3ea3211f4376bda5d7b6e8d
Author: root <r...@evhubudsd23bb.budapest.epam.com>
Date:   2015-10-16T05:45:14Z

Merge branch 'master' into ignite-1371




---
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.
---