GitHub user Xiao-zhen-Liu created a discussion: Let Frontend Pass Physical Plan to ComputingUnit
In the current Texera architecture (shown below), we have two compliers, one being the `WorkflowCompilingService`, the other `WorkflowCompiler` in the `ComputingUnit`. <img width="1212" height="467" alt="image" src="https://github.com/user-attachments/assets/cbf96d85-96fb-4b56-8440-232aeb78fcaa"; /> In the codebase they are mostly duplicated code. We should get rid of `WorkflowCompiler` eventually to avoid this duplication. The main blocker currently is that `WorkflowCompiler` is a part of the execution engine (shown below), which accepts a logical plan from the frontend, and relies on the `WorkflowCompiler` to produce a physical plan. <img width="787" height="697" alt="image" src="https://github.com/user-attachments/assets/36726f3c-9e30-4ef8-a137-2eaabb52ea4d"; /> If we allow the frontend to pass a physical plan to ComputingUnit instead, We can remove `WorkflowCompiler` and keep only `WorkflowCompilingService`. GitHub link: https://github.com/apache/texera/discussions/4167 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
