[SPARK-3641] Correctly populate SparkPlan.currentContext

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.1.0
• Fix Version/s: 1.2.0
• Component/s: SQL
• Target Version/s: 1.2.0
• Assignee: Michael Armbrust
• Reporter: Yin Huai
• Created: 22/Sep/14 15:57
• Updated: 02/Dec/14 20:16
• Resolved: 03/Oct/14 19:36

Description

After creating a new SQLContext, we need to populate SparkPlan.currentContext before we create any SparkPlan. Right now, only SQLContext.createSchemaRDD populate SparkPlan.currentContext. SQLContext.applySchema is missing this call and we can have NPE as described in http://qnalist.com/questions/5162981/spark-sql-1-1-0-npe-when-join-two-cached-table.

Issue Links

• Is contained by: SPARK-3212 Improve the clarity of caching semantics