jerryshao commented on issue #12716: URL: https://github.com/apache/gravitino/issues/12716#issuecomment-5698063173
Hi @neoLsH, sorry for the slow follow-up on my side, and sorry for the overlap this creates. While working through the broader epic I ended up putting together an implementation for this subtask myself — apache/gravitino#13250. It landed on a fairly similar shape to what you outlined (fetch-on-demand from the executor rather than persisted, capped/tailed output, exposed via the existing `getJob` path), so a good chunk of your analysis is reflected in it. Since you clearly put a lot of thought into the design, I'd really appreciate it if you could take a look at the PR and let me know what you think — especially anywhere it diverges from what you had in mind. Thanks again for the detailed write-up, it was genuinely useful context even though I didn't loop back in time. -- 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]
