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 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 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 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 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 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 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 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 user agoncharuk closed the pull request at:
https://github.com/apache/ignite/pull/5229
---
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 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 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 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 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 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 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 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 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 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 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 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 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 and
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 and
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 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 user agoncharuk closed the pull request at:
https://github.com/apache/ignite/pull/3182
---
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 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 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 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 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 and
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 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 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 and
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 and
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/3182
ignite-gg-13116
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-13116
Alternatively you can review and
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 and
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 and
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 and
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 and
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/2351
8.0.3.ea13
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.ea13
Alternatively you can review and
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 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 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 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 and
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 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 is
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 is
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 is
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 is
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 is
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 and
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 and
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 and
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 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 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 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 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 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 is
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 and
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/634
IGNITE-2954 - Added tests for various read-through scenarios
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agoncharuk/ignite ignite-2954
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/509
Ignite-2709 - Fixed stack overflow for contented puts.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2709
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/508
Ignite-2707 - Fixed skipStore flag handling.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2707
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 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 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 is
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 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 is
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 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 is
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 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 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 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 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 user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/355
IGNITE-2209 - Fixing class casts in query tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agoncharuk/ignite ignite-2209
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 is
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 user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/348
IGNITE-2194 - Fixed cache proxy deserialization.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agoncharuk/ignite ignite-2194
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 is
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 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 these
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 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 is
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 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 is
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 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 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 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 is
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 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 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
94 matches
Mail list logo
