[SPARK-20149] Audit PySpark code base for 2.6 specific work arounds

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Done
• Affects Version/s: 2.2.0
• Component/s: PySpark
• Assignee: Unassigned
• Reporter: Holden Karau
• Created: 30/Mar/17 00:36
• Updated: 12/Dec/22 18:10
• Resolved: 07/Jun/17 09:29

Description

We should determine what the areas in PySpark are that have specific 2.6 work arounds and create issues for them. The audit can be started during 2.2.0, but cleaning up all the 2.6 specific code is likely too much to try and get in so the actual fixing should probably be considered for 2.2.1 or 2.3 (unless 2.2.0 is delayed).