Feature Request / Improvement
It would be worth adding a timeout option for the main syncing function to allow the system to return back to normal to investigate the problem without entering into resource leak problem linked to the execution or a costly cloud execution without full knowledge of the required time.
It is as basically saying I expect this sync to complete in less than 30 minutes, if not than it is not worth it before some data are changed before resyncing.
This feature can be valuable especially for full-sync of large tables.
May require the use of https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html in XTableSync class' runSync())
[### Are you willing to submit PR?
Code of Conduct
Feature Request / Improvement
It would be worth adding a timeout option for the main syncing function to allow the system to return back to normal to investigate the problem without entering into resource leak problem linked to the execution or a costly cloud execution without full knowledge of the required time.
It is as basically saying I expect this sync to complete in less than 30 minutes, if not than it is not worth it before some data are changed before resyncing.
This feature can be valuable especially for full-sync of large tables.
May require the use of
https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.htmlin XTableSync class' runSync())[### Are you willing to submit PR?
Code of Conduct