buvb commented on issue #2128: URL: https://github.com/apache/fluss/issues/2128#issuecomment-3635624856
@luoyuxia For general dual-write consistency issues, the conventional approach is to use a two-phase commit solution. However, I think this solution might be too complex. I propose a mechanism that involves synchronizing first, applying the changes, and then compensating. The method is as follows: 1. First verify that the schema change is valid in both Fluss and Paimon. 2. First, sync to Paimon. 3. Update Fluss schema 4. If Fluss fails, record the inconsistency and trigger an alarm. 5. When Tiering, perform compatibility processing based on the schema version. you can assign it to me. -- 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]
