GitHub user parshimers added a comment to the discussion: Proposal: Unify Backend Resource Management On Texera
Looks like a great idea to me. A good time to do it as well. Catalog cleanups never get easier. It makes sense that it was kind of done in an ad-hoc way at first, that's just natural. One thought is that, if we are going to change the paths for some things, would it make sense to add a version prefix on to the path at this point? Or, perhaps the headers if there is preference about keeping the paths clean? That way if something has to change later, it will make life easier to control the compatibility between different services. GitHub link: https://github.com/apache/texera/discussions/9395#discussioncomment-19663909 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
