Let Frontend Pass Physical Plan to ComputingUnit #4167
Xiao-zhen-Liu
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In the current Texera architecture (shown below), we have two compliers, one being the

WorkflowCompilingService, the otherWorkflowCompilerin theComputingUnit.In the codebase they are mostly duplicated code. We should get rid of
WorkflowCompilereventually to avoid this duplication.The main blocker currently is that

WorkflowCompileris a part of the execution engine (shown below), which accepts a logical plan from the frontend, and relies on theWorkflowCompilerto produce a physical plan.If we allow the frontend to pass a physical plan to ComputingUnit instead, We can remove
WorkflowCompilerand keep onlyWorkflowCompilingService.Beta Was this translation helpful? Give feedback.
All reactions