[SPARK-33139] protect setActiveSession and clearActiveSession

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 3.1.0
• Fix Version/s: 3.1.0
• Component/s: SQL
• Assignee: jiahong.li
• Reporter: Leanken.Lin
• Created: 14/Oct/20 02:01
• Updated: 09/Feb/21 01:30
• Resolved: 13/Nov/20 13:38

Description

This PR is a sub-task of SPARK-33138(https://issues.apache.org/jira/browse/SPARK-33138). In order to make SQLConf.get reliable and stable, we need to make sure user can't pollute the SQLConf and SparkSession Context via calling setActiveSession and clearActiveSession.

Change of the PR:

• add legacy config spark.sql.legacy.allowModifyActiveSession to fallback to old behavior if user do need to call these two API.
• by default, if user call these two API, it will throw exception
• add extra two internal and private API setActiveSessionInternal and clearActiveSessionInternal for current internal usage
• change all internal reference to new internal API exception for SQLContext.setActive and SQLContext.clearActive

Issue Links

• links to: [Github] Pull Request #30042 (leanken)
• links to: [Github] Pull Request #30042 (leanken)
• links to: [Github] Pull Request #30092 (leanken)
• links to: [Github] Pull Request #30092 (leanken)
• links to: [Github] Pull Request #30362 (leanken)
• links to: [Github] Pull Request #30367 (leanken)