ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From yzhdanov <...@git.apache.org>
Subject [GitHub] ignite pull request: Ignite disabled per-partition map
Date Mon, 25 Jan 2016 18:49:13 GMT
GitHub user yzhdanov opened a pull request:


    Ignite disabled per-partition map


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

    $ git pull https://github.com/yzhdanov/ignite ignite-disabled-perpartition-map

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


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #423
commit 914b365f79311e56c46ee4e214f60d60753030cc
Author: Yakov Zhdanov <yzhdanov@gridgain.com>
Date:   2016-01-25T18:34:43Z

    fixed https://issues.apache.org/jira/browse/IGNITE-2329 + forceKeysFuture opts

commit 3f1ab4dac0f85729026fd06eec97e9d2e3e002fa
Author: Yakov Zhdanov <yzhdanov@gridgain.com>
Date:   2016-01-25T18:48:17Z

    fixed https://issues.apache.org/jira/browse/IGNITE-2329 + forceKeysFuture opts + disabled
partition map


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 infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message