Re: [PR] Metadata location fallback [iceberg-python]

2025-02-13 Thread via GitHub
IsaacWarren closed pull request #1658: Metadata location fallback URL: https://github.com/apache/iceberg-python/pull/1658 -- 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 uns

Re: [PR] Metadata location fallback [iceberg-python]

2025-02-13 Thread via GitHub
IsaacWarren commented on PR #1658: URL: https://github.com/apache/iceberg-python/pull/1658#issuecomment-2657153561 It was a create table transaction so it makes sense it was null. I think I was confused that metadata-location and table_metadata.location were equivalent but on further readin

Re: [PR] Metadata location fallback [iceberg-python]

2025-02-12 Thread via GitHub
kevinjqliu commented on PR #1658: URL: https://github.com/apache/iceberg-python/pull/1658#issuecomment-2655346808 hey @IsaacWarren what operations were you performing when you encountered the issue above? was it a create_table or load_table or something else? > don't populate tab

[PR] Metadata location fallback [iceberg-python]

2025-02-12 Thread via GitHub
IsaacWarren opened a new pull request, #1658: URL: https://github.com/apache/iceberg-python/pull/1658 Some REST catalogs (Polaris when I was testing an Azure catalog) don't populate table_response.metadata_location but they do populate table_response.metadata.location. This PR just falls ba