InvisibleProgrammer commented on PR #11041:
URL: https://github.com/apache/iceberg/pull/11041#issuecomment-3709796824

   Hi, I'm not an Iceberg contributor, I'm just heavily interested in 
implementing this feature in Hive. 
   Please allow me to add a couple of questions about this specification (And 
also, please correct me in case I'm interpreting something wrong): 
   
   - 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 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. 
   
   And lastly please let me bring up a question about the timeline: as I see, 
this discussion goes for more than a year. I wonder, is there a way to speed 
the planning phase up? Iceberg is well known as a project evolving fast. I know 
there are still open questions and fine tuning. What about making an agreement 
on a minimal version that can work, saying that is the format-version 2 accept 
it, let the engines implement their part and making an agreement about the 
final, well-detailed version (maybe format-version 3) after gathering 
experience of the version 2? 
   
   I really appreciate your hard work, I believe materialized view will be a 
great Iceberg feature.
   
   Thank you, 
   Zsolt


-- 
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]

Reply via email to