[SPARK-23486] LookupFunctions should not check the same function name more than once

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.1, 2.3.0
• Fix Version/s: 2.4.0
• Component/s: SQL
• Labels: starter
• Assignee: kevin yu
• Reporter: Cheng Lian
• Created: 22/Feb/18 01:13
• Updated: 13/Jul/18 05:19
• Resolved: 13/Jul/18 05:19

Description

For a query invoking the same function multiple times, the current LookupFunctions rule performs a check for each invocation. For users using Hive metastore as external catalog, this issues unnecessary metastore accesses and can slow down the analysis phase quite a bit.

Issue Links

• is caused by: SPARK-19737 New analysis rule for reporting unregistered functions without relying on relation resolution
• links to: [Github] Pull Request #20795 (kevinyu98)