zhangshenghang commented on PR #12409:
URL: https://github.com/apache/seatunnel/pull/12409#issuecomment-6731043251

   Issue 1 is fixed in ee9e797f0 (both languages). The heartbeat section no 
longer promises idle-periodic execution: it now says SQL Server's polling loop 
does not dispatch idle heartbeats on its own and the action runs only when the 
connector actually emits a heartbeat. The closing paragraph no longer implies 
heartbeats protect against cleanup — it now states cleanup is retention-based 
with or without heartbeats, and that the retention window must be sized to keep 
checkpoint-relevant LSN rows available across outages and lag, with cleanup/lag 
monitoring.
   
   On Issue 2 (zh GraphQL "exponential" backoff): I could not locate an 
exponential-backoff claim on the zh GraphQL page at the current head — the 
retry rows describe `retry_backoff_multiplier_ms` / `retry_backoff_max_ms` 
without naming the curve. It looks like that wording is already gone; if you 
still see it, please point me at the line and I will fix it.
   
   An empty "Trigger CI" commit (70a834d7c) was pushed on top so the fork's 
Build workflow runs on the new head.
   


-- 
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]

Reply via email to