prestodb/presto

Optimize ARBITRARY(NULL)

Open

#21,590 opened on Dec 21, 2023

View on GitHubContributor guide
 (5 comments) (0 reactions) (1 assignee)Java (5,240 forks)batch import
Query Optimizationgood first issueoptimizer

Repository metrics

Stars
 (15,558 stars)
PR merge metrics
 (Avg merge 34d 14h) (120 merged PRs in 30d)

Description

We see these operations frequently and can be very expensive. So it will be good to optimizer them to NULL in the expression optimizers upfront before other optimizations

Contributor guide

Research direction
Examine the expression optimizer code in Presto's query planner to understand how ARBITRARY(NULL) is currently handled and identify where to optimize it to NULL before other optimizations.
Tech stack
java
Domain
database
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
SQLJava
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30