GitHub user Xiao-zhen-Liu added a comment to the discussion: Proposal: Unify Backend Resource Management On Texera
I support this direction. Consolidating ownership, access control, and CRUD removes substantial duplication across services and makes adding new kinds like operators straightforward. Two suggestions for the detailed design: 1. Decouple metadata and access primitives from the storage layer. A workflow version stores a JSON patch in PostgreSQL, while dataset and model versions commit files to LakeFS. Treating the version record as metadata referencing a kind-specific storage handler keeps the common schema clean. 2. Plan an incremental transition for REST routes. The frontend and agent service rely on endpoints like `/workflow/create` and `/workflow/persist`. Supporting legacy routes as adapters prevents breaking client flows while unified endpoints roll out. GitHub link: https://github.com/apache/texera/discussions/9395#discussioncomment-19575758 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
