jackye1995 commented on issue #7151:
URL: https://github.com/apache/iceberg/issues/7151#issuecomment-1477134680
Thank you for the detailed explanation and proposals.
My concern of the option is that it has performance implications, as we will
take much longer to retry a commit compared to just determine based on
optimistic locking failure.
I am wondering if there is a way for AWS client to stop retry if it hits
service unavailable. I think we can do that through AWS client configuration,
like:
```
GlueClient.builder()
.overrideConfiguration(ClientOverrideConfiguration.builder()
.retryPolicy(RetryPolicy.builder()
.retryCondition(xxx) // some custom impl we can develop
for Glue to not retry on service unavailable error or read timeout
.build())
.build())
```
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
