GitHub user zyratlo added a comment to the discussion: Proposal: Unify Backend 
Resource Management On Texera

I support this as well. Right now each resource kind works like its own small 
system, and like you pointed out, that shows up for users too, since sharing a 
workflow and sharing a dataset don't behave the same way. One definition of a 
resource that every kind follows makes sense, especially with agents, 
conversations, and operators likely coming later.

I'm curious about how resources refer to each other. A workflow already uses 
datasets, and the kinds you listed would probably reference other resources as 
well. The lineage table links a version to the versions it was derived from, 
but I didn't see where "this workflow uses this dataset version" would live. Is 
that meant to be one of the common primitives too, or left for each kind to 
handle on its own?

GitHub link: 
https://github.com/apache/texera/discussions/9395#discussioncomment-19575594

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to