nssalian opened a new issue, #1149: URL: https://github.com/apache/iceberg-go/issues/1149
### Feature Request / Improvement The table package is up to ~37 source files now, all flat in one directory. Core stuff like table.go and metadata.go sits next to the fanout writers, the scanner, transaction/commit code, and the maintenance tools. It's come up in review a few times and was brought up in [Slack](https://apache-iceberg.slack.com/archives/C05J3MJ42BD/p1780302482426819). How I'd approach breaking it up: - design the layout first - short writeup plus one package pulled out as a prototype to see what the API churn really looks like - then land it one package at a time Timing-wise I think this is a post-v3 thing. I don't want to step on the core work that's in flight. Filing now so it's on the radar. I can work on this and start looking at what would be good organizations for the code. Will share when I have something. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
