ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9180) IgniteSparkSession Should Copy State on cloneSession()
Date Thu, 23 Aug 2018 05:25:00 GMT

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

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

Github user asfgit closed the pull request at:

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


> IgniteSparkSession Should Copy State on cloneSession()
> ------------------------------------------------------
>
>                 Key: IGNITE-9180
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9180
>             Project: Ignite
>          Issue Type: Bug
>          Components: spark
>    Affects Versions: 2.6
>            Reporter: Stuart Macdonald
>            Assignee: Stuart Macdonald
>            Priority: Major
>             Fix For: 2.7
>
>
> The IgniteSparkSession class extends SparkSession and overrides the cloneSession() method.
The contract for cloneSession() explicitly states that it should clone all state (ie. the
sharedState and sessionState fields), however the IgniteSparkSession implementation doesn't clone its
state fields.
> This has the side-effect of breaking stateful operations for anything which uses cloneSession(),
for example a Spark streaming job will not be able to use cached data across streaming
microbatches, which is a significant issue for such applications.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message