[ 
https://issues.apache.org/jira/browse/IGNITE-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295073#comment-15295073
 ] 

ASF GitHub Bot commented on IGNITE-2929:
----------------------------------------

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 <[email protected]>
Date:   2016-05-21T15:07:02Z

    fix the wrong type parameters of IgniteContext

----


> IgniteContext should not have type parameters
> ---------------------------------------------
>
>                 Key: IGNITE-2929
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2929
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 1.5.0.final
>            Reporter: Valentin Kulichenko
>             Fix For: 1.7
>
>
> 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.
> Looks like type parameters on {{IgniteContext}} don't make much sense and 
> should be removed. {{fromCache}} method should be parameterized instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to