[GitHub] ignite pull request #5534: IGNITE-10484 Fixed activate/deactivate hang

2018-11-29 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5534 IGNITE-10484 Fixed activate/deactivate hang You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10484

[GitHub] ignite pull request #5486: IGNITE-10390 Fixed BPlusTree#isEmpty

2018-11-23 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5486 IGNITE-10390 Fixed BPlusTree#isEmpty You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10390 Alternatively you

[GitHub] ignite pull request #5483: IGNITE-10381 Fixed U.doInParallel early terminati...

2018-11-22 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5483 IGNITE-10381 Fixed U.doInParallel early termination You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10381

[GitHub] ignite pull request #5436: IGNITE-10043 Do not reset LOST partitions when on...

2018-11-19 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5436 IGNITE-10043 Do not reset LOST partitions when only one node is left in a cluster You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[GitHub] ignite pull request #5433: IGNITE-10044 Proper LOST partitions handling

2018-11-19 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5433 IGNITE-10044 Proper LOST partitions handling You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10044

[GitHub] ignite pull request #5378: IGNITE-10237 Fixed inspections

2018-11-13 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5378 IGNITE-10237 Fixed inspections You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10237 Alternatively you can

[GitHub] ignite pull request #5237: IGNITE-10123 Disable events in IgniteLogicalRecov...

2018-11-02 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5237 IGNITE-10123 Disable events in IgniteLogicalRecoveryTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite

[GitHub] ignite pull request #5231: IGNITE-9720 Lazy free lists

2018-11-01 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5231 IGNITE-9720 Lazy free lists You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9720 Alternatively you can

[GitHub] ignite pull request #5229: IGNITE-9730 Lazy free lists

2018-11-01 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/5229 ---

[GitHub] ignite pull request #5229: IGNITE-9730 Lazy free lists

2018-11-01 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5229 IGNITE-9730 Lazy free lists You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9720 Alternatively you can

[GitHub] ignite pull request #5224: IGNITE-10064 Fixed examples pom files

2018-10-31 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5224 IGNITE-10064 Fixed examples pom files You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10064 Alternatively

[GitHub] ignite pull request #5208: IGNITE-10011 Fixed pages leak

2018-10-30 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5208 IGNITE-10011 Fixed pages leak You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10011 Alternatively you can

[GitHub] ignite pull request #5000: IGNITE-9895 DiscoveryMessageNotifierWorker must b...

2018-10-16 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5000 IGNITE-9895 DiscoveryMessageNotifierWorker must be instanceof IgniteDiscoveryThread You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #4930: IGNITE-9822 Fix WAL archiver stop logic

2018-10-09 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/4930 IGNITE-9822 Fix WAL archiver stop logic You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9822 Alternatively

[GitHub] ignite pull request #4929: IGNITE-9821 rebuildIndexesFromHash should not thr...

2018-10-09 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/4929 IGNITE-9821 rebuildIndexesFromHash should not throw exception …tion You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #4924: IGNITE-9784 Automatically adjust max WAL history ...

2018-10-08 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/4924 IGNITE-9784 Automatically adjust max WAL history size …mance drop You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #4886: IGNITE-8803 Corrected output for quiet mode

2018-10-02 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/4886 IGNITE-8803 Corrected output for quiet mode You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8803

[GitHub] ignite pull request #4694: SchemaExchangeSelfTest added correct IP finder

2018-09-06 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/4694 SchemaExchangeSelfTest added correct IP finder You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-scexch

[GitHub] ignite pull request #4691: IGNITE-9479 Fixed spontaneous rebalance during ca...

2018-09-06 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/4691 IGNITE-9479 Fixed spontaneous rebalance during cache start …ed logging level You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[GitHub] ignite pull request #4690: Ignite 2.5.1 p12 notrace

2018-09-05 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/4690 Ignite 2.5.1 p12 notrace You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p12-notrace Alternatively

[GitHub] ignite pull request #4588: IGNITE-9326 Fixed node failure processor invocati...

2018-08-21 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/4588 IGNITE-9326 Fixed node failure processor invocation when EntryProcess… …or result serialization throws an exception You can merge this pull request into a Git repository by running

[GitHub] ignite pull request #3892: Ignite-2.5.1.b5

2018-04-20 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3892 Ignite-2.5.1.b5 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1.b5 Alternatively you can review

[GitHub] ignite pull request #3862: Ignite-8082 ZK MBean

2018-04-18 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3862 Ignite-8082 ZK MBean You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8082 Alternatively you can review

[GitHub] ignite pull request #3821: IGNITE-8258 Fixed page acquire/write unlock order...

2018-04-13 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3821 IGNITE-8258 Fixed page acquire/write unlock order during checkpoint You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3753: Attempting to fix hanging suite

2018-04-05 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3753 Attempting to fix hanging suite You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13667 Alternatively you

[GitHub] ignite pull request #3182: ignite-gg-13116

2018-02-15 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/3182 ---

[GitHub] ignite pull request #3455: IGNITE-7577 Fixing public API active flag on base...

2018-01-30 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3455 IGNITE-7577 Fixing public API active flag on baseline changes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite

[GitHub] ignite pull request #3454: IGNITE-7569 Fixed index rebuild future

2018-01-30 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3454 IGNITE-7569 Fixed index rebuild future You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7569 Alternatively

[GitHub] ignite pull request #3434: Ignite-2.4-comp-check

2018-01-25 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3434 Ignite-2.4-comp-check You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4-comp-check Alternatively you can

[GitHub] ignite pull request #3340: ignite-2.4.1 reconnect fix

2018-01-09 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3340 ignite-2.4.1 reconnect fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.1-merge-master-recFix

[GitHub] ignite pull request #3323: ignite-2.4.1-p7

2017-12-29 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3323 ignite-2.4.1-p7 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.1-p7 Alternatively you can review

[GitHub] ignite pull request #3290: Ignite 7308

2017-12-26 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3290 Ignite 7308 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7308 Alternatively you can review and apply

[GitHub] ignite pull request #3279: ignite-2.4.2

2017-12-22 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3279 ignite-2.4.2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.2 Alternatively you can review and apply

[GitHub] ignite pull request #3239: ignite-2.4.1-p6

2017-12-15 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3239 ignite-2.4.1-p6 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.1-p6 Alternatively you can review

[GitHub] ignite pull request #3191: ignite-2.4.1-p4

2017-12-09 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3191 ignite-2.4.1-p4 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.1-p4 Alternatively you can review

[GitHub] ignite pull request #3164: ignite-2.4.1-p2

2017-12-06 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3164 ignite-2.4.1-p2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.1-p2 Alternatively you can review

[GitHub] ignite pull request #3122: Ignite-2.4.1-p1

2017-12-01 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3122 Ignite-2.4.1-p1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.1-p1 Alternatively you can review

[GitHub] ignite pull request #2471: 8.0.3.ea15

2017-08-17 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/2471 8.0.3.ea15 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.3.ea15 Alternatively you can review

[GitHub] ignite pull request #2385: 8.0.3.ea14

2017-08-03 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/2385 8.0.3.ea14 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.3.ea14 Alternatively you can review

[GitHub] ignite pull request #2296: Ignite-2.1.3

2017-07-13 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/2296 Ignite-2.1.3 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1.3 Alternatively you can review and apply

[GitHub] ignite pull request #2249: Ignite-2.1.2

2017-07-06 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/2249 --- 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

[GitHub] ignite pull request #2249: Ignite-2.1.2

2017-07-05 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/2249 Ignite-2.1.2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.1.2 Alternatively you can review and apply

[GitHub] ignite pull request #2007: gg-8.0.3.ea9

2017-05-25 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/2007 gg-8.0.3.ea9 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.3.ea9 Alternatively you can review

[GitHub] ignite pull request #1965: Ignite gg 8.0.3.ea8

2017-05-17 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/1965 Ignite gg 8.0.3.ea8 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.3.ea8 Alternatively you can

[GitHub] ignite pull request #343: IGNITE-2178 - Fixed primary key set for scan query...

2017-05-12 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/343 --- 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

[GitHub] ignite pull request #348: IGNITE-2194 - Fixed cache proxy deserialization.

2017-05-12 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/348 --- 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

[GitHub] ignite pull request #332: Ignite 2100

2017-05-12 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/332 --- 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

[GitHub] ignite pull request #42: Ignite 264

2017-05-12 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/42 --- 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

[GitHub] ignite pull request #471: Ignite 2396 - Service deployment for dynamic cache...

2017-05-12 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/471 --- 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

[GitHub] ignite pull request #1279: gg-8.0.1.ea7

2016-11-24 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/1279 gg-8.0.1.ea7 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.1.ea7 Alternatively you can review

[GitHub] ignite pull request #1256: gg-8.0.1.ea6

2016-11-22 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/1256 gg-8.0.1.ea6 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.1.ea6 Alternatively you can review

[GitHub] ignite pull request #1154: gg-8.0.0.ea4

2016-10-10 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/1154 gg-8.0.0.ea4 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.0.ea4 Alternatively you can review

[GitHub] ignite pull request #1119: GG-11547 - RWLock tags

2016-09-27 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/1119 GG-11547 - RWLock tags You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11547 Alternatively you can review

[GitHub] ignite pull request #1056: Cluster state and lost partitions handling

2016-09-15 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/1056 --- 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

[GitHub] ignite pull request #1064: EA1

2016-09-15 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/1064 EA1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.0.ea1 Alternatively you can review and apply

[GitHub] ignite pull request #1056: Cluster state and lost partitions handling

2016-09-12 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/1056 Cluster state and lost partitions handling You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-10882

[GitHub] ignite pull request #914: ignite-1.6.4

2016-08-01 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/914 ignite-1.6.4 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.6.4 Alternatively you can review and apply

[GitHub] ignite pull request #837: Ignite gg 11275

2016-06-28 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/837 --- 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

[GitHub] ignite pull request #837: Ignite gg 11275

2016-06-28 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/837 Ignite gg 11275 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11275 Alternatively you can review

[GitHub] ignite pull request: Ignite 2610 - Fixed excessive memory usage in...

2016-02-16 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/488 Ignite 2610 - Fixed excessive memory usage in TTL manager You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2610

[GitHub] ignite pull request: IGNITE-2396 - Fixed service deployment for dy...

2016-02-10 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/432 --- 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

[GitHub] ignite pull request: Ignite 2396 - Service deployment for dynamic ...

2016-02-10 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/471 Ignite 2396 - Service deployment for dynamic caches You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2396

[GitHub] ignite pull request: ignite-2325 - Fixing assertion on prepare fut...

2016-01-28 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/390 --- 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

[GitHub] ignite pull request: ignite-2325 - Fixing assertion on prepare fut...

2016-01-28 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/434 ignite-2325 - Fixing assertion on prepare future remap. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2325

[GitHub] ignite pull request: IGNITE-2396 - Fixed service deployment on cac...

2016-01-28 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/416 --- 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

[GitHub] ignite pull request: IGNITE-2396 - Fixed service deployment for dy...

2016-01-28 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/432 IGNITE-2396 - Fixed service deployment for dynamic cache creation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite

[GitHub] ignite pull request: IGNITE-2396 - Fixed service deployment on cac...

2016-01-22 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/416 IGNITE-2396 - Fixed service deployment on cache creation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2396

[GitHub] ignite pull request: IGNITE-2434 - Do not update cache store if en...

2016-01-22 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/418 IGNITE-2434 - Do not update cache store if entry processor was a noop. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite

[GitHub] ignite pull request: IGNITE-2099 - Fixing custom collections.

2016-01-12 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/396 IGNITE-2099 - Fixing custom collections. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2099 Alternatively you

[GitHub] ignite pull request: ignite-2325 - Fixing assertion on prepare fut...

2015-12-30 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/390 ignite-2325 - Fixing assertion on prepare future remap. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2325

[GitHub] ignite pull request: IGNITE-2200 - Fixed deployment and added a te...

2015-12-23 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/367 IGNITE-2200 - Fixed deployment and added a test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2200

[GitHub] ignite pull request: IGNITE-2201 - Fixed affinity collocation with...

2015-12-18 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/352 IGNITE-2201 - Fixed affinity collocation with AffinityKey and examples model You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk

[GitHub] ignite pull request: IGNITE-2201 - Fixed affinity collocation with...

2015-12-18 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/352 --- 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

[GitHub] ignite pull request: IGNITE-2138 Introduced toBuilder() method.

2015-12-16 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/330 --- 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

[GitHub] ignite pull request: IGNITE-2178 - Fixed primary key set for scan ...

2015-12-16 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/343 IGNITE-2178 - Fixed primary key set for scan query. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2178

[GitHub] ignite pull request: Ignite 2100

2015-12-14 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/332 Ignite 2100 You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2100 Alternatively you can review and apply

[GitHub] ignite pull request: IGNITE-2138 Introduced toBuilder() method.

2015-12-14 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/330 IGNITE-2138 Introduced toBuilder() method. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2138 Alternatively you

[GitHub] ignite pull request: IGNITE-2098 - Added test for java proxy.

2015-12-10 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/301 --- 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

[GitHub] ignite pull request: IGNITE-2124 - Do not notify DS manager for us...

2015-12-10 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/313 IGNITE-2124 - Do not notify DS manager for user caches, use correct simple names for queries You can merge this pull request into a Git repository by running: $ git pull https

[GitHub] ignite pull request: IGNITE-2100 - Fixes for Externalizable classe...

2015-12-10 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/311 --- 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

[GitHub] ignite pull request: IGNITE-2100 - Fixes for Externalizable classe...

2015-12-09 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/311 IGNITE-2100 - Fixes for Externalizable classes and queries. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2100

[GitHub] ignite pull request: IGNITE-2098 - Added test for java proxy.

2015-12-08 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/301 IGNITE-2098 - Added test for java proxy. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2098 Alternatively you

[GitHub] ignite pull request: IGNITE-2050 - Remove duplicates from the conf...

2015-12-03 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/291 IGNITE-2050 - Remove duplicates from the configuration. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2050

[GitHub] ignite pull request: Fixing hang in metadata update.

2015-11-28 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/280 Fixing hang in metadata update. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-1282 Alternatively you can review

[GitHub] ignite pull request: Fixing hang in metadata update.

2015-11-28 Thread agoncharuk
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/280 --- 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

[GitHub] ignite pull request: Ignite 264

2015-08-26 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/42 Ignite 264 You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-264 Alternatively you can review and apply these changes

[GitHub] ignite pull request: Ignite-1281 - Improvements in communication m...

2015-08-24 Thread agoncharuk
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/32 Ignite-1281 - Improvements in communication messages. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-1281