GitHub user mengw15 added a comment to the discussion: Proposal: Unify Backend Resource Management On Texera
I agree with this direction. This would be a great opportunity to consolidate and refactor our existing resource management mechanisms. I believe it would make our codebase much cleaner and easier to maintain. One concern I have is that different resources may have their own resource-specific operations and permissions. Would it make sense to keep the common CRUD and access control primitives while allowing each resource type to define additional operations and permission checks? This way, we could maintain a consistent foundation while preserving the flexibility needed for different resources. GitHub link: https://github.com/apache/texera/discussions/9395#discussioncomment-19577130 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
