[GitHub] ignite pull request #1506: IGNITE-4302 binary metadata component refactored ...

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

[GitHub] ignite pull request #1506: IGNITE-4302 binary metadata component refactored ...

andrey-kuznetsov
GitHub user sergey-chugunov-1985 opened a pull request:

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

    IGNITE-4302 binary metadata component refactored to use discovery-based protocol

    Metadata updates are exchanged using DiscoveryCustomMessage-based protocol instead of utility cache.

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

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

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

    https://github.com/apache/ignite/pull/1506.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 #1506
   
----
commit fc5bf177ad1c81f8e59d9ba0cbf37b327b5a9e94
Author: Sergey Chugunov <[hidden email]>
Date:   2017-01-19T13:53:34Z

    IGNITE-4302 implementation of DiscoveryCustomEvent-based binary metadata exchange component

----


---
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 #1506: IGNITE-4302 binary metadata component refactored ...

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

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


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