adamcodes716 commented on issue #1680:
URL: 
https://github.com/apache/iceberg-python/issues/1680#issuecomment-2669420605

   > > why is this URL being generated using load_catalog? the "/iceberg" 
shouldn't be part of the url.
   > 
   > The pyiceberg rest client takes the `uri` specified in `load_catalog` as 
the base url and calls Iceberg rest endpoints using it. So for the uri you 
specified, 
`http://localhost:19120/iceberg/v1/config?warehouse=s3%3A%2F%2Fwarehouse`, the 
`http://localhost:19120/iceberg` part is from the `uri` configured. The 
`/v1/config` is a standard iceberg rest endpoint.
   > 
   > For any `uri` given to `load_catalog`, pyiceberg's rest client will call 
`{uri}/v1/config`.
   > 
   > > I think the issue that so many people are having is trying to get the 
right combination of code and settings to get all of this to work. I do have a 
request open in the nessie area, but they often point back here because 
load_catalog isn't theirs.
   > 
   > Yea i've seen different issues of connecting to Nessie. I'm confused by 
the docs actually. 
[Here](https://iceberg.apache.org/docs/1.7.0/nessie/#nessie-catalog) the docs 
mentions that `https://localhost:19120/api/v2` is the `uri` for rest endpoint. 
But 
[here](https://projectnessie.org/nessie-latest/trino/#starter-configuration) 
the uri is `http\://localhost\:33405/iceberg/`
   
   Thanks for the reply!   So I've been down the road of using /api instead of 
/iceberg.  I got a 200 on the connection, but I was unable to get past these 
errors:
   
   ```
   Field required [type=missing, input_value={'defaultBranch': 
'main',...SupportedApiVersion': 2}, input_type=dict]
   For further information visit https://errors.pydantic.dev/2.6/v/missing
   ```
   
   Others had the same issue, and then apparently solved them by using 
/iceberg.  And round and round we go.   Have you successfully  configured 
Nessie?


-- 
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

Reply via email to