Translating Expressions through Coral
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 906
- Forks
- 219
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 2
Description
Can Coral provide stable APIs to translate expressions from hive to Presto through coral?
Usecase (As requested by Praveen Krishna):
Presto allows connectors to provide row-filters in terms of expressions. It's possible that they're defined in hiveql, and presto needs to read and transform them before applying. For this purpose, having the ability to translate expressions directly is useful.
for example, Presto can be configured to say that for queries by user U on on table tpch.tiny.orders , exclude rows for which orderKey is >= 10. This is defined as an expression written as orderKey < 10 in the configuration. Currently, Presto requires this expression to be in a form that Presto can understand. If coral allows hive --> presto translation of such expressions, then they could be expressed as hive expressions and translated at runtime.
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 by surveying Coral's current translation capabilities and public API boundaries for Hive and Presto expressions. Clarify whether runtime expression translation is in scope, which expression forms must be supported, and how successful translation should be verified; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100