Add config exchange.azure.max-error-retries

[linzebing]

Description

Is this change a fix, improvement, new feature, refactoring, or other?

New config

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

trino-exchange-filesystem plugin

How would you describe this change to a non-technical end user or system administrator?

This PR allows users to configure the maximum number of request error retries fro Azure-based spooling. Default was 4, now 10.

Related issues, pull requests, and links

Documentation

( ) No documentation is needed.
(x) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

(x) No release notes entries required.
( ) Release notes entries required with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

[colebow]

I'm going to propose that we add a release note for this:

## General
Add `exchange.azure.max-error-retries` configuration property for the
number of retries performed when accessing Azure blob storage. ({issue}`13663`)

Does that seem ok? And would it be better if it went into a different or more specific section?

[arhimondr]

It looks good to me. @linzebing Do we usually put changes to exchange manager into a dedicated section?

[linzebing]

@colebow: I don't expect most users need to change this config in practice. So I would suggest we don't do a release note for this.

[rijojoseph07]

Hi @linzebing we are currently using fs.azure.io.retry.max.retries to control retries at the driver level. How is this config different? Thanks

[linzebing]

@rijojoseph07 : This one is set for the client side. I don't know which one takes precedence for Azure.