kevinjqliu commented on issue #1589: URL: https://github.com/apache/iceberg-python/issues/1589#issuecomment-2646412685
> Obviously, when configuring the client, I'll need to use 3 different URLs depending on these 3 conditions, but the server will always return the same URL in the /config endpoint. So you can connect to the same server with different uri schemes. For example, * ALB (alb://server) * Private link (private://server) * Proxy (proxy://server) And the server advertise its own address as http://server. When connecting using the REST client, the `catalog.uri` gets overwritten? `uri` is part of [catalog properties](https://iceberg.apache.org/docs/latest/configuration/#catalog-properties) so it makes sense that it is allowed to be overwritten by the server. I think the easiest solution is to have the server not send the optional `uri` properties in the response. I understand the concern and need for more control over the REST client. As part of the REST spec, the client and server should both be working together and adhering to the spec. Of course, you can always implement custom logic on top of existing components. -- 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
