[IGNITE-9180] IgniteSparkSession Should Copy State on cloneSession()

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6
• Fix Version/s: 2.7
• Component/s: spark
• Assignee: Stuart Macdonald
• Reporter: Stuart Macdonald
• Created: 03/Aug/18 11:35
• Updated: 23/Aug/18 05:24
• Resolved: 23/Aug/18 05:21

Description

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.

Issue Links

• links to: GitHub Pull Request #4531