zeroshade commented on PR #58:
URL: https://github.com/apache/iceberg-go/pull/58#issuecomment-1942110612
@nastra So I've figured out the issue:
The properties are correctly being propagated to the FileIO object, however
it looks like the tabular api doesn't like the Go Iceberg user-agent.
I loaded up `pyiceberg` to see what it does differently and how it works,
and saw that the request for the table included in its response a series of s3
properties including an access-key-id, session-token, and secret-access-key in
the config. When I looked at the same request from the Go cli those properties
weren't there. If I hardcode and change the User-Agent that the Go CLI passes
to be `PyIceberg/0.5.1` suddenly those properties are returned and loading the
manifests works just fine. So the problem is definitely the fact that the
User-Agent isn't recognized by the tabular rest catalog enough for it to send
the s3 key properties.
Anything we can do on the tabular side?
During `RestCatalog.LoadTable`
--
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
