[GitHub] ignite pull request: [IGNITE-2929] IgniteContext should not have t...

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

[GitHub] ignite pull request: [IGNITE-2929] IgniteContext should not have t...

andrey-kuznetsov
GitHub user f7753 opened a pull request:

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

    [IGNITE-2929] IgniteContext should not have type parameters

    Currently implementation of `SparkContext` has type parameters `[K, V]` which means that all the RDDs that are created by a particular instance of context have to be of the same type.
    Type parameters on`IgniteContext` is removed.`fromCache` method is parameterized instead.

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

    $ git pull https://github.com/f7753/ignite rdd-fix

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

    https://github.com/apache/ignite/pull/740.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 #740
   
----
commit 069bcf448f2e09d7d7f0080b6803559661bc35af
Author: MaBiao <[hidden email]>
Date:   2016-05-21T15:07:02Z

    fix the wrong type parameters of IgniteContext

----


---
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 #740: IGNITE-2929 IgniteContext should not have type par...

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

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


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