SQL operators should have overloading resolved statically
Open
dsl
improvement
P3
sql
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
Currently, operators like `>, ``<=`, and others dynamically dispatch on the type of their operands. But SQL is statically typed, and we should both validate the types (if Calcite doesn't do it for us) and gain performance by avoiding this dispatch.
Imported from Jira [BEAM-4703](https://issues.apache.org/jira/browse/BEAM-4703). Original Jira may contain additional context.
Reported by: kenn.
Contributor guide
Research direction
Start by tracing Apache Beam's SQL operator handling and how Calcite validates operand types, focusing on the dynamic dispatch mentioned in the issue. Done means SQL operators have statically resolved overloads, operand types are validated, and the dynamic dispatch is avoided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100