[GitHub] ignite pull request #2074: IGNITE 5368 Cassandra store should support privat...

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

[GitHub] ignite pull request #2074: IGNITE 5368 Cassandra store should support privat...

andrey-kuznetsov
GitHub user irudyak opened a pull request:

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

    IGNITE 5368 Cassandra store should support private/public fields serialization for POJO persistence strategy

   

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

    $ git pull https://github.com/irudyak/ignite ignite-5368

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

    https://github.com/apache/ignite/pull/2074.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 #2074
   
----
commit d44fdd452125a7735ec4718b18a7dcea5a95f471
Author: Igor Rudyak <[hidden email]>
Date:   2017-06-03T05:54:15Z

    ignite-5368

commit e773c4bc166fd304f54689d11ce9038c58412825
Author: Igor Rudyak <[hidden email]>
Date:   2017-06-03T05:56:26Z

    Merge branch 'master' into ignite-5368

----


---
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 #2074: IGNITE 5368 Cassandra store should support privat...

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

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


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