danielcweeks commented on PR #12827: URL: https://github.com/apache/iceberg/pull/12827#issuecomment-2816031634
@singhpk234 > My only concern with the following was each client maintaining its own connection pool, with large number of prefixes, which would not be scalable IMHO > and each cred provider will do a refresh logic and get the cred for the the path it corresponds to I don't think we would expect that there are going to be large numbers of prefixes. A table will typically have just a single prefix. We're trying to support cases where there are multiple but also cannot express the policy within the size limits of a single credential. Reusing the client would address these concerns, but I don't think we even need to address that case unless it's trivial to do as part of this support. I feel like the `ExecutionInterceptor` approach is optimizing for the wrong goals and we can address those in a different way. I'd rather be consistent than clever here since we need to support it across multiple implementations. -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
