Investigate using SqlBasicCall in SqlCallTransformer
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 906
- Forks
- 219
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 2
Description
Current [SqlCallTransformer](https://github.com/linkedin/coral/blob/master/coral-common/src/main/java/com/linkedin/coral/common/transformers/SqlCallTransformer.java#L22) transforms `SqlCall`, we need to investigate if transforming `SqlBasicCall` meets our requirement of migrating transformations from RelNode layer to SqlNode layer.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with coral-common/src/main/java/com/linkedin/coral/common/transformers/SqlCallTransformer.java and inspect how it currently transforms SqlCall. Compare the requirements for using SqlBasicCall and the planned migration from the RelNode layer to the SqlNode layer. Done means documenting or demonstrating whether SqlBasicCall satisfies those transformation requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100