snazy commented on PR #1128: URL: https://github.com/apache/polaris/pull/1128#issuecomment-2729817856
> Can you point out in the code where "exposes persistence internals and pushes those things up to the call sites"? I'm also open for suggestion how we can separate concern better. Sure, as mentioned elsewhere, there should eventually be distinct APIs for each concern. Those APIs do not have to and therefore must not deal for example with persistence-internal IDs or dictate how objects are stored but provide the "concern specific" operations. As that's a more general approach, I really prefer to move this one into draft state and discuss the approach on the dev-ML. -- 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: issues-unsubscr...@polaris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
