[GitHub] ignite pull request #1310: IGNITE-4355: (1) double checked locking in Hadoop...

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

[GitHub] ignite pull request #1310: IGNITE-4355: (1) double checked locking in Hadoop...

andrey-kuznetsov
GitHub user iveselovskiy opened a pull request:

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

    IGNITE-4355: (1) double checked locking in HadoopShuffle, (2) lazy co…

    …ntext init in HadoopShuffleJob.

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

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

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

    https://github.com/apache/ignite/pull/1310.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 #1310
   
----
commit 3f8a35019ff5b7e06f365cf63d7dc041f9c80859
Author: iveselovskiy <[hidden email]>
Date:   2016-12-02T10:53:34Z

    IGNITE-4355: (1) double checked locking in HadoopShuffle, (2) lazy context init in HadoopShuffleJob.

----


---
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 #1310: IGNITE-4355: (1) double checked locking in Hadoop...

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

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


---
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.
---