mjsax edited a comment on pull request #10953: URL: https://github.com/apache/kafka/pull/10953#issuecomment-878690334
> Otherwise, Streams app that run with 2.8 and before might not be compatible with Streams 3.0 because the retention time of the changelog topics created with older Streams apps will be smaller than the assumed retention time for Streams apps in 3.0. Why would this be fatal? It seems in 3.0 the retention time would potentially become _larger_ (if a new changlog topic is created). And for any existing application, we won't reconfigure the topic config. While I agree that we should keep the behavior in-sync, I don't see how there could be data loss? -- Note that if the old behavior has a shorter retention time, it would be a "bug" if the state store keeps stuff longer now (even if retention-time is a _lower_ bound an keeping stuff longer is still correct; retention it's not a strict bound), but it won't be a regression with regard to data loss, as we never guaranteed to keep the data longer than in the old behavior case. -- 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: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
