[GitHub] ignite pull request #1028: Ignite 1.6.6 p1

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

[GitHub] ignite pull request #1028: Ignite 1.6.6 p1

andrey-kuznetsov
GitHub user devozerov opened a pull request:

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

    Ignite 1.6.6 p1

   

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

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

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

    https://github.com/apache/ignite/pull/1028.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 #1028
   
----
commit 12fd4976f482ebc43831754645e34042c9073b2d
Author: sboikov <[hidden email]>
Date:   2016-08-25T09:29:04Z

    Fixed GridQueryParsingTest.

commit 8c56e4516e55c7ed9c14779f0e77e00f055d9a81
Author: vozerov-gridgain <[hidden email]>
Date:   2016-09-02T15:05:16Z

    IGNITE-3827: Removed double marshalling of keys in DataStreamerImpl.addData(Map) method.

commit 4dc624fc9a8852f77f1fe7db4dc06a474b34c2eb
Author: vozerov-gridgain <[hidden email]>
Date:   2016-09-02T15:23:09Z

    IGNITE-3829: Optimized affinity key field name handling.

----


---
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 #1028: Ignite 1.6.6 p1

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

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


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