GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/2238
ignite-5693
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5693
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2238.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 #2238
----
commit a5abdd579cc7ace5d17ebcc6555e3ce66c777917
Author: Vasiliy Sisko <vsi...@gridgain.com>
Date: 2017-07-04T11:44:42Z
ignite-2.1 Fixed minor issues and typos.
commit 6c9d2228d2aba6ba5be64bd20ef244e634aeaa5a
Author: Alexey Kuznetsov <akuznet...@apache.org>
Date: 2017-07-04T12:30:46Z
ignite-2.1 Added persistent store metrics.
commit b69f53e0ccf9d3da42a99d4423fb3d8bdd60a7bb
Author: Pavel Tupitsyn <ptupit...@apache.org>
Date: 2017-07-04T14:42:31Z
IGNITE-5629 .NET: CacheConfiguration copy constructor
commit 2e7adbfbbab62f3b98e0409d2f4ceabad89b4120
Author: agura <ag...@gridgain.com>
Date: 2017-07-04T13:56:40Z
ignite-5685 JDBC prepared statement shouldn't clear parameters after
execution
commit 31dc7ba80cf44b299eed9f7cece09e47a2dc44bc
Author: Ilya Lantukh <ilant...@gridgain.com>
Date: 2017-07-04T17:04:08Z
ignite-5693 : Fixed flaky test.
----
---
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.
---
