generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 49
Open
2 / 52 of 5 issues completedLabels
MetaMeta issue, not directly linked to a PRMeta issue, not directly linked to a PRenhancementNew feature or requestNew feature or request
Description
Is your feature request related to a problem?
Unifying function behavior removes a major source of drift between engines and lets the PPL frontend stay portable. Today, many PPL UDFs/UDAFs have their definitions and implementations tightly coupled to Calcite APIs. This leads to duplicated engine-specific function code paths, and friction when porting these PPL functions to other engine such as Spark.
What solution would you like?
Proposed approach:
unified-query-apimodule provides engine-independentUnifiedFunctionandUnifiedFunctionRepositoryabstraction.- Spark integrates unified function into Catalyst expression system by a thin
UnifiedFunctionSparkWrapper
What alternatives have you considered?
[Update after PoC]
Do you have any additional context?
N/A
Reactions are currently unavailable
Sub-issues
Metadata
Metadata
Assignees
Labels
MetaMeta issue, not directly linked to a PRMeta issue, not directly linked to a PRenhancementNew feature or requestNew feature or request
Type
Projects
Status
New