[GitHub] ignite pull request #1623: Implement NoopEventStorageSpi and make default
GitHub user alpert opened a pull request: https://github.com/apache/ignite/pull/1623 Implement NoopEventStorageSpi and make default You can merge this pull request into a Git repository by running: $ git pull https://github.com/alpert/ignite ignite-4812 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1623.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 #1623 commit 492650ddc7334dcf4841fb2f2a424407527d8200 Author: alpert Date: 2017-03-14T20:49:39Z Implement NoopEventStorageSpi and make default --- 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: Format miliseconds as they will be 3 digits
Github user alpert closed the pull request at: https://github.com/apache/ignite/pull/534 --- 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: Filter client nodes when loading caches
Github user alpert closed the pull request at: https://github.com/apache/ignite/pull/719 --- 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: Filter client nodes when loading caches
GitHub user alpert opened a pull request: https://github.com/apache/ignite/pull/719 Filter client nodes when loading caches That fixes https://issues.apache.org/jira/browse/IGNITE-2394. If to call cache.loadCache(...) then the loading from a storage would happen on all the nodes including client nodes. Now we are only loading to data nodes instead of all cache nodes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/alpert/ignite IGNITE-2394 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/719.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 #719 commit 807db0834ed822675670c0fcf873379475d269d6 Author: alpert Date: 2016-05-14T15:53:03Z Filter client nodes when loading caches That fixes https://issues.apache.org/jira/browse/IGNITE-2394. If to call cache.loadCache(...) then the loading from a storage would happen on all the nodes including client nodes. Now we are only loading to data nodes instead of all cache nodes. --- 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: Format miliseconds as they will be 3 digits
GitHub user alpert opened a pull request: https://github.com/apache/ignite/pull/534 Format miliseconds as they will be 3 digits Fixes #517 You can merge this pull request into a Git repository by running: $ git pull https://github.com/alpert/ignite IGNITE-2690 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/534.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 #534 commit 119b063018a4d349f08d13b8ead39c58d07466e0 Author: alpert Date: 2016-03-03T17:20:44Z Format miliseconds as they will be 3 digits --- 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. ---
