ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gvvinblade <...@git.apache.org>
Subject [GitHub] ignite pull request #2401: ignite-2.1.3.b1
Date Fri, 04 Aug 2017 17:02:32 GMT
GitHub user gvvinblade opened a pull request:

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

    ignite-2.1.3.b1

    

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

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

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

    https://github.com/apache/ignite/pull/2401.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 #2401
    
----
commit eb336074c91da2e35aab4ca9f69a5d7191b3701b
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 8356ae7ac06eca77ed2a8c70b2cf86bc5d700fb6
Author: Igor Seliverstov <gvvinblade@gmail.com>
Date:   2017-08-04T12:14:03Z

    IGNITE-5658 Optimizations for data streamer
    IGNITE-5918 Adding and searching objects in index tree produces a lot of garbage
    IGNITE-5921 Reduce contention for free list access

commit 67c3833e835ff9d4a1880e984dd6446d431fd4a1
Author: Igor Seliverstov <gvvinblade@gmail.com>
Date:   2017-08-04T16:51:43Z

    IGNITE-5658 Optimizations for data streamer

----


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

Mime
View raw message