[GitHub] ignite pull request #1736: IGNITE-4917: BinaryObjectBuilder field value acce...

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

[GitHub] ignite pull request #1736: IGNITE-4917: BinaryObjectBuilder field value acce...

andrey-kuznetsov
GitHub user AMashenkov opened a pull request:

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

    IGNITE-4917: BinaryObjectBuilder field value access failed if its serialized with optimal marshaller

    Fixed failure when accessing BinaryObjectBuilder field value serialized with OptimizedMarshaller.

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

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

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

    https://github.com/apache/ignite/pull/1736.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 #1736
   
----
commit 1fcf992b30d86ad0c34df82c7a6afb5c52ac6106
Author: Andrey V. Mashenkov <[hidden email]>
Date:   2017-04-05T11:33:27Z

    Fixed failure when accessing BinaryObjectBuilder field value serialized with OptimizedMarshaller .

----


---
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 #1736: IGNITE-4917: BinaryObjectBuilder field value acce...

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

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


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