luoyuxia commented on PR #1940: URL: https://github.com/apache/fluss/pull/1940#issuecomment-3742622396
@LiebingYu The latter approach (ignoring tiering progress after disabling) might lead to silent data loss. For users, this is often an "unexpected behavior." If data correctness issues occur because the data was deleted before being successfully tiered, it becomes extremely difficult for us to troubleshoot and recover. We should require an explicit "force" flag or a specific confirmation if they truly want to bypass the tiering safety check. I still prefer to not to do ttl when user disable the data lake. Realistically, if a user has already enabled the data lake, the scenarios where they would want to permanently disable it may be rare(I'm not sure the real 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
