GitHub user zyratlo added a comment to the discussion: Two efforts to convert a Python program to a Texera workflow
I agree with the plan. Since the LLM tool is already merged, gathering feedback on it first makes sense, and that feedback should show us pretty directly whether users need the equivalence guarantee or the privacy the compiler gives. I also agree with Chen's point about the critical path. Both the LLM and compiler tools are fairly separate from the engine, so a bug in either one doesn't have big consequences for the rest of Texera. That makes me comfortable keeping the compiler maintained outside main for now, as long as it stays current enough that merging it later isn't a big effort if the feedback shows a need. I agree that since a significant amount of time and effort has been put into the compiler, we shouldn't abandon it. Putting it on a different fork and maintaining it there sounds like a good compromise. Since the current compiler implementation is still a MVP and doesn't support translating many Python capabilities yet, I wonder when it would be ready to start testing and benchmarking on real programs. GitHub link: https://github.com/apache/texera/discussions/8521#discussioncomment-18685060 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
