ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From EdShangGG <...@git.apache.org>
Subject [GitHub] ignite pull request #2423: IGNITE-5943
Date Wed, 09 Aug 2017 15:59:41 GMT
GitHub user EdShangGG opened a pull request:




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

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

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 #2423
commit 2d93a7c11871a2b23cfb2e6f9854dccb48eac4f1
Author: Andrey Novikov <anovikov@gridgain.com>
Date:   2017-08-03T03:42:08Z

    IGNITE-5888 Web Console: Fixed maven project generation.

commit 36787e149693103fa22ba4093259d2fd8425689a
Author: Andrey Novikov <anovikov@gridgain.com>
Date:   2017-08-03T03:45:59Z

    IGNITE-5906 Fixed race on activities merge.

commit 9e9f1d1e4cdcb3ade018f3eabcf2b2d10a7c003b
Author: tledkov-gridgain <tledkov@gridgain.com>
Date:   2017-08-04T08:16:52Z

    IGNITE-5920: Fixed CacheClientBinaryQueryExample": set CacheKeyConfiguration explicitly
to enable affinity co-location. This closes #2389.

commit 944056e5431b6018bb653c563db1356f0148fb9a
Author: anovikov <anovikov@gridgain.com>
Date:   2017-08-04T11:10:36Z

    IGNITE-5908 Restore splash.

commit a1652b8f7748d3bf1e42437f9ad36f6f44e19bf5
Author: Sergey Chugunov <sergey.chugunov@gmail.com>
Date:   2017-08-07T08:34:01Z

    IGNITE-5950 incorrect assertion fixed

commit cfa5ac269c37718191be42d5554637b78c2a7466
Author: Eduard Shangareev <eshangareev@gridgain.com>
Date:   2017-08-09T15:57:24Z

    IGNITE-5943 Communication. Server node may reject client connection during massive clients


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