jasonhughes248 opened a new pull request #2622: URL: https://github.com/apache/iceberg/pull/2622
while working on additional educational materials for iceberg (will be making them public shortly), I found making a few changes to the table format diagram on https://iceberg.apache.org/spec/#overview helped people better tie the higher level architecture diagram to what they were seeing in the filesystem as operations were made. changes made to the diagram: - added iceberg catalog because it's a component of the table format and because it shows the starting point for all operations against that table - within the catalog, show visually that there can be multiple tables stored in the catalog, so it shows that you don't need a separate discovery service to find each iceberg table in your environment - put db1.table1 to show that this is a sample table name and that the other boxes behind it are additional tables that are in the catalog, but I'm not very partial on keeping vs changing vs removing the sample table name - named the reference to the current metadata file in the iceberg catalog "current metadata pointer" because I'm not aware if there is an official term for what this pointer/reference is called. if there is, or if there's a better name someone wants to suggest, I'm happy to change it - added metadata file boxes and labels around the snapshot objects because metadata files were missing as a file type and snapshot pointers are within the metadata files, rather than being their own files, like the rest of the other boxes in the diagram I used the png from the site which looks a little more compressed than how I saved it, so there's a little difference between the sharpness of the text and lines of the current content vs the additions. I'm happy to make the changes on the original if you want to share the original chart with me cc @rymurr -- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
