DanielLeens commented on issue #10918: URL: https://github.com/apache/seatunnel/issues/10918#issuecomment-4608236539
The direction is useful, but cache design can become too broad very quickly. I would treat the source-of-truth rule and the invalidation contract as the two must-have design points here: when provider, model, dimension, modality, or chunk hash changes, exactly which cache key becomes invalid, and what behavior is expected after retry / restart. Keeping the in-process cache strictly as an optimization layer, not a correctness dependency, is the right design boundary. -- 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]
