DanielLeens commented on issue #13184:
URL: https://github.com/apache/seatunnel/issues/13184#issuecomment-6739657846

   Thanks for defining the opt-in contract carefully. The default of one 
attempt and the separation from ambiguous transport failures are the right 
compatibility boundaries.
   
   Please do not start the LLM retry implementation yet. #13177 and #13179 are 
active prerequisites for the shared Retry-After path and safe diagnostics; a 
parallel retry implementation now could duplicate or bypass their error 
classification. Once their final contracts are available, rebase on them and 
open one focused PR for this issue.
   
   That PR must prove: default configurations still issue exactly one request; 
valid seconds and HTTP-date Retry-After values take the longer delay; malformed 
and over-cap values follow the stated failure/fallback behavior; interrupted 
waits make no further call; retryable and non-retryable status matrices are 
preserved; and a non-idempotent CUSTOM endpoint can observe duplicate attempts 
only when the user explicitly opts in. Please keep retry state invocation-local 
and avoid adding persistence or new dependencies.


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