You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by GitBox <gi...@apache.org> on 2022/07/29 17:11:42 UTC
[GitHub] [iceberg] flyrain commented on pull request #5378: Hive: More distinctive cached client pool key to avoid conflict
flyrain commented on PR #5378:
URL: https://github.com/apache/iceberg/pull/5378#issuecomment-1199767818
> @flyrain: Why do we need to have a different HiveClientPool? Do these pools have a different configuration?
Yes, it needs different config(`metastore.catalog.default`).
Once a client pool is created and cached, we don't reset its default catalog, so we can never visit the second catalog with the same uri. For example, `ClientPool1(uri1, catalog1)` is cached and always be used, but we need another one `ClientPool1(uri1, catalog2)` to visit the second catalog.
--
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-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org