tanishqgandhi1908 commented on PR #6502: URL: https://github.com/apache/texera/pull/6502#issuecomment-5027944692
Thanks again @Yicong-Huang. I think prefix-required + a one-time migration would be a better approach than keeping datasets unprefixed. Reason: with models getting their own table, the leading segment is what tells the resolver which table to look in, so an unprefixed path can't be routed unambiguously. Making the prefix required keeps a single, self-describing path shape. Migration (one-time via Liquibase): - Only touches the fileName property in workflow.content / workflow_version.content. - Every existing path is a dataset (identified by the owner-email first segment), so it's a blanket `"/<owner>/…"` → `"/datasets/<owner>/…"`. More context and the design (with diagrams) are in this discussion — happy to go deeper there: #6616 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
