You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are the path URIs intended to be fully addressable, such as within the location or metadata-file fields?
From the example given in the spec with a path of s3://bucket/.../v1.json to some table metadata JSON, this would be missing a region configuration and would be down to a client implementation to set AWS_REGION=YOUR_REGION or configured in some other way.
For some extra context, I asked this question in the Iceberg Slack and believe I understand the answer, but wanted to make it more discoverable for others who are searching issues.
I'd also like to ask whether there is anywhere within the spec I can add this information? My original thought was within the implementation notes, but it is not clear to me whether this is the correct place.
The text was updated successfully, but these errors were encountered:
Query engine
N/A
Question
Are the path URIs intended to be fully addressable, such as within the
location
ormetadata-file
fields?From the example given in the spec with a path of
s3://bucket/.../v1.json
to some table metadata JSON, this would be missing a region configuration and would be down to a client implementation to setAWS_REGION=YOUR_REGION
or configured in some other way.For some extra context, I asked this question in the Iceberg Slack and believe I understand the answer, but wanted to make it more discoverable for others who are searching issues.
I'd also like to ask whether there is anywhere within the spec I can add this information? My original thought was within the implementation notes, but it is not clear to me whether this is the correct place.
The text was updated successfully, but these errors were encountered: