[SPARK-45660] Re-use Literal objects when replacing timestamps in the ComputeCurrentTime rule

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.5.0
• Fix Version/s: 4.0.0
• Component/s: Optimizer
• Labels: pull-request-available
• Assignee: Jan-Ole Sasse
• Reporter: Jan-Ole Sasse
• Created: 25/Oct/23 06:12
• Updated: 25/Oct/23 16:56
• Resolved: 25/Oct/23 16:56

Description

The ComputeCurrentTime optimizer rule does produce unique timestamp Literals for current time expressions of a query. For CurrentDate and LocalTimestamp objects only the literal objects are not re-used though, but equal objects are created for each instance. This can cost unnecessary much memory in case there are many such Literal objects.

Issue Links

• links to: GitHub Pull Request #43524