[GitHub] ignite pull request #932: Ignite 1.7.2

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #932: Ignite 1.7.2

andrey-kuznetsov
GitHub user devozerov opened a pull request:

    https://github.com/apache/ignite/pull/932

    Ignite 1.7.2

   

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-1.7.2

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/932.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 #932
   
----
commit 78a21f100849dfbd2c3663a79c701e892a836618
Author: vozerov-gridgain <[hidden email]>
Date:   2016-08-05T12:05:32Z

    IGNITE-3631: IGFS: Now metadata co-location is used for PARTITIONED cache as well.

commit bb0fb7293b7e430431e7699101320f59b3b93067
Author: vozerov-gridgain <[hidden email]>
Date:   2016-08-05T12:05:43Z

    IGNITE-3631: IGFS: Now metadata co-location is used for PARTITIONED cache as well.

commit 8dd39a59b0b530af215473d2be3a9107f6ca71e1
Author: tledkov-gridgain <[hidden email]>
Date:   2016-08-09T07:01:56Z

    IGNITE-3332: IGFS: Optimized file unlock routine with help of a client callable. This closes #916.

----


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #932: Ignite 1.7.2

andrey-kuznetsov
Github user asfgit closed the pull request at:

    https://github.com/apache/ignite/pull/932


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---