[GitHub] ignite pull request #926: IGNITE-3263 Affinity function must check for null ...

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

[GitHub] ignite pull request #926: IGNITE-3263 Affinity function must check for null ...

andrey-kuznetsov
GitHub user samaitra opened a pull request:

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

    IGNITE-3263 Affinity function must check for null keys

   

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

    $ git pull https://github.com/samaitra/ignite IGNITE-3263

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

    https://github.com/apache/ignite/pull/926.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 #926
   
----
commit 4a09b4598b8a0210af45bf738d634768fa9619a3
Author: samaitra <[hidden email]>
Date:   2016-08-05T16:49:28Z

    IGNITE-3263 Affinity function must check for null keys

commit 88d85f5572df6040e924a7024c9906238a005392
Author: samaitra <[hidden email]>
Date:   2016-08-05T16:51:13Z

    Merge remote-tracking branch 'upstream/master' into IGNITE-3263

commit 7bfac77cb6ef0099b45151733d66457186c87cc5
Author: samaitra <[hidden email]>
Date:   2016-08-05T16:58:10Z

    IGNITE-3263 Affinity function must check for null keys

----


---
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 #926: IGNITE-3263 Affinity function must check for null ...

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

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


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