Fokko commented on issue #78:
URL: https://github.com/apache/iceberg-python/issues/78#issuecomment-1771214572
I have the same feeling, I think this should be done once, and not every
time you initialize the catalog (if you run a lot of jobs in parallel using
Airflow, these calls can add up)
gkaretka commented on issue #78:
URL: https://github.com/apache/iceberg-python/issues/78#issuecomment-1771206442
Maybe this issue can be renamed into: _documentation_ rather than _bug_.
What do you think @mobley-trent
--
This is an automated message from the Apache Git Service.
To respon
gkaretka commented on issue #78:
URL: https://github.com/apache/iceberg-python/issues/78#issuecomment-1770748027
Thanks 👍 was actually trying to investigate a little further and came to the
same conclusion. Creating tables by calling:
`catalog.create_tables()`
solved my problem
Fokko commented on issue #78:
URL: https://github.com/apache/iceberg-python/issues/78#issuecomment-1770729964
@mobley-trent @gkaretka Thanks for reaching out here. The tables are not
created by default, but I think that might be the wrong behaviour since you
both expected them to be created
gkaretka commented on issue #78:
URL: https://github.com/apache/iceberg-python/issues/78#issuecomment-1770718118
👍 same issue
--
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.
mobley-trent opened a new issue, #78:
URL: https://github.com/apache/iceberg-python/issues/78
### Apache Iceberg version
0.5.0 (latest release)
### Please describe the bug 🐞
Python = 3.11
PostgreSql = v16
I'm having issues setting up the initial connection to po
