difin commented on PR #6449: URL: https://github.com/apache/hive/pull/6449#issuecomment-4615780770
> On conceptional level, I have two major questions: Should the Rest client handle views as tables? Or views should be views? At the current implementation it mixes them and basic CRUD operations doesn't separate them. For example, listing tables can receive both tables and views. But we don't know if a given entry is a table or a view. Same as https://github.com/apache/hive/pull/6449#discussion_r3346172004, answered there. > > The other important question is the boundary between what we store on HMS and what we store on Iceberg side? What happens if we create a native Iceberg view? Do we store the metadata only on Iceberg side? Or duplicate it between Hive and Iceberg? What if we duplicate them? How we can make sure the duplicated data is in sync? And what is the plan if it is not in sync? For example, I'm creating a native Iceberg view in Beeline. Connect to the Rest client. Modify the view. Go back to Hive and query this view. What will happen? Also answered before: HMS stores only the view identity and HMS table that is constructed at query time is enriched in-memory from the Iceberg metadata (including View SQL text) on both HMS and REST client paths. -- 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]
