GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/1619
IGNITE-4802
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/ignite ignite-4802
Alternatively you can review and apply these
Github user vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/1619
---
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 vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/1785
IGNITE-4954 - Configurable expiration timeout for Casssndra session
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/ignite
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/850
Ignite 2949
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/ignite ignite-2949
Alternatively you can review and apply these changes
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/1369
IGNITE-4439 - Attribute based node filter
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/ignite ignite-4439
Alternatively
Github user vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/1369
---
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 vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/26
IGNITE-1280
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite ignite-1280
Alternatively you can review and apply
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/27
IGNITE-884 (Cache store usability issues)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite ignite-884
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/69
IGNITE-1378 - Fixed exception handling in GridContinuousProcessor.staâ¦
â¦rtRoutine()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Github user vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/69
---
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 vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/82
IGNITE-1402 - Fixed logging categories
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite ignite-1402
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/83
IGNITE-1378 - Fixed exception handling in GridContinuousProcessor
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator
Github user vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/82
---
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 vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/83
---
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 vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/103
IGNITE-1522 - Made cache entry listener configurations transient
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator
Github user vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/103
---
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 vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/104
IGNITE-1536 - Removed duplicated continuous query notifications
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator
Github user vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/104
---
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 vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/127
Fixed race in GridDhtForceKeysRequest processing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite ignite-force
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/153
IGNITE-1622 - Fixed cache.clear() with near cache
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite ignite-1622
Github user vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/153
---
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 vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/163
IGNITE-1702 - Fixed error handling for cache updates
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite ignite
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/222
Do not destroy LOCAL cache on close()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite
ignite-local-cache
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/226
Reusing message reader per NIO session
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite
ignite-direct-marsh
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/318
IGNITE-2105 - Fixed nested collections in direct marshalling
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite
Github user vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/318
---
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 vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/364
IGNITE-2249 - Do not deserialize services on client node
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite
GitHub user vkulichenko opened a pull request:
https://github.com/apache/ignite/pull/405
Switch off update notifier
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkulichenko/incubator-ignite gg-10952
Alternatively you can
Github user vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/405
---
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 vkulichenko closed the pull request at:
https://github.com/apache/ignite/pull/364
---
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
30 matches
Mail list logo
