Fokko closed issue #365: Implement Centralized Management of Table Properties
URL: https://github.com/apache/iceberg-python/issues/365
--
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 co
HonahX commented on issue #365:
URL: https://github.com/apache/iceberg-python/issues/365#issuecomment-1928871173
I can take this if no one has started it :).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abov
HonahX commented on issue #365:
URL: https://github.com/apache/iceberg-python/issues/365#issuecomment-1928773118
@Fokko Sounds good. My initial thought was to use a new file because
table/__init__.py already has a substantial amount of content, and it's likely
to grow as we develop write su
Fokko commented on issue #365:
URL: https://github.com/apache/iceberg-python/issues/365#issuecomment-1928022429
I think this is a great idea @HonahX. I try to avoid creating a lot of new
files, since imports in Python are slow. What do you think of adding a class
`TableProperties` to `table
HonahX opened a new issue, #365:
URL: https://github.com/apache/iceberg-python/issues/365
### Feature Request / Improvement
With the release of version 0.6.0, pyiceberg is set to expand its
capabilities in handling a greater variety of table properties, encompassing
both read and wri
