GitHub user sshiv012 added a comment to the discussion: Two efforts to convert a Python program to a Texera workflow
Since the LLM-based approach has already been merged, I think our immediate priority should be gathering user feedback and improving that experience. We should let concrete user needs guide whether we maintain a second conversion path. Privacy and security requirements are a separate consideration that we can evaluate when users raise them, including whether **model providers offer appropriate compliance assurances and deployment options**. I would avoid making those hypothetical requirements the deciding factor today. I support continuing the compiler work in a fork, where it can mature and be evaluated. I appreciate the substantial effort already invested, and I’m happy to help review and evaluate it as it improves. Preserving that work gives us a valuable option while we learn more from users. I’m open to bringing it into Texera once we have a demonstrated need, a mature MVP, and a clear justification for the ongoing maintenance cost. My emphasis would be on user experience, correctness, and code maintainability. A concrete next step would be to agree on a benchmark suite, an evaluation owner, and a review date, alongside collecting feedback on the LLM approach. That gives the compiler effort a clear path forward and lets us make the merge decision based on evidence. GitHub link: https://github.com/apache/texera/discussions/8521#discussioncomment-18684799 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
