[
https://issues.apache.org/jira/browse/HADOOP-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-19805:
------------------------------------
Description:
When creating a signer for s3 (or another service), if it is Configurable, call
setConf() on it.
This comes from me wiring s3a up to iceberg RestCatalog; it's pretty convoluted
to connect a signer in the sdk to its owner fs otherwise, and so get the
configuration for that bucket. Trivial change.
(w.r.t the old convolutedness: a v1 issue). For v2 we can create and configure
the signer then attach it: nothing else needed!
was:
When creating a signer for s3 (or another service), if it is Configurable, call
setConf() on it.
This comes from me wiring s3a up to iceberg RestCatalog; it's pretty convoluted
to connect a signer in the sdk to its owner fs otherwise, and so get the
configuration for that bucket. Trivial change.
> When creating a signer, if it is Configurable, set its config
> -------------------------------------------------------------
>
> Key: HADOOP-19805
> URL: https://issues.apache.org/jira/browse/HADOOP-19805
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 3.4.3
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Trivial
> Labels: pull-request-available
> Fix For: 3.5.0, 3.4.3
>
>
> When creating a signer for s3 (or another service), if it is Configurable,
> call setConf() on it.
> This comes from me wiring s3a up to iceberg RestCatalog; it's pretty
> convoluted to connect a signer in the sdk to its owner fs otherwise, and so
> get the configuration for that bucket. Trivial change.
> (w.r.t the old convolutedness: a v1 issue). For v2 we can create and
> configure the signer then attach it: nothing else needed!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
