stevenzwu commented on PR #11041: URL: https://github.com/apache/iceberg/pull/11041#issuecomment-3873040325
@InvisibleProgrammer looks like we missed your earlier questions/comments > There is a field in view metadata called format-version. The spec says it should be 1. Can the format version be changed with this specification? I believe you are talking about the view format version in the view spec. Since we are not introducing breaking changes to the view spec. We don't need to bump up the view spec version. > was thinking about the storage table: at this point if we pick up a table, we just don't know if it is a storage table of a materialized view or just a regular table. Can the table metadata get a reference to the materialized view in case it is a storage table of a view? It would help other engines to protect the storage table from accidental table operations: if the engine is more strict, it can completely hides that table or disallow to do DML operations on that. If the engine less strict it can completely ignore that field. MV storage tables have the `refresh-state` to distinguish with regular tables. Yes, engines are recommended to protect the storage tables from direct DMLs and only allow MV refresh operations. Catalogs (especially REST) also plays an important role here. E.g., REST catalog may return the view and storage table metadata in one response. > And lastly please let me bring up a question about the timeline We made a lot progress, compromises, and consensus in the last a few months. I believe we have reached consensus in the current spec/design discussion for at least the initial phase. Agree with you that we can still evolve and improve the spec in the future. -- 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]
