GitHub user CaroFernando added a comment to the discussion: Proposal: Unify Backend Resource Management On Texera
I support this idea. It would directly help #9362, which I’m looking into: loading operators at runtime instead of compiling them into the system. With the common primitives, operators could simply be another resource kind. Publishing an operator would create an immutable version, saved workflows could pin the operator version they were built with, and access control would decide who can use each operator, all without building a separate set of tables and endpoints just for operators. That would let the operator work focus on the engine side (registering and loading operators at runtime) instead of resource management. GitHub link: https://github.com/apache/texera/discussions/9395#discussioncomment-19575335 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
