Hi, FWIW, in Trino we just added Trino views support. https://github.com/trinodb/trino/pull/8540 Of course, this is by no means usable by other query engines.
Anjali, your document does not talk much about compatibility between query engines. How do you plan to address that? For example, I am familiar with Coral, and I appreciate its powers for dealing with legacy stuff like views defined by Hive. I treat it as a great technology supporting transitioning from a query engine to a better one. However, I would not base a design of some new system for storing cross-engine compatible views on that. Is there something else we can use? Maybe the view definition should use some intermediate structured language that's not SQL? For example, it could represent logical structure of operations in semantics manner. This would eliminate need for cross-engine compatible parsing and analysis. Best PF On Tue, Jul 20, 2021 at 11:04 AM Ryan Murray <rym...@gmail.com> wrote: > Thanks Anjali! > > I have left some comments on the document. I unfortunately have to miss > the community meetup tomorrow but would love to chat more/help w/ > implementation. > > Best, > Ryan > > On Tue, Jul 20, 2021 at 7:42 AM Anjali Norwood > <anorw...@netflix.com.invalid> wrote: > >> Hello, >> >> John Zhuge and I would like to propose the following spec for storing >> view metadata in Iceberg. The proposal has been implemented [1] and is in >> production at Netflix for over 15 months. >> >> >> https://docs.google.com/document/d/1wQt57EWylluNFdnxVxaCkCSvnWlI8vVtwfnPjQ6Y7aw/edit?usp=sharing >> >> [1] >> https://github.com/Netflix/iceberg/tree/netflix-spark-2.4/view/src/main/java/com/netflix/bdp/view >> >> Please let us know your thoughts by adding comments to the doc. >> >> Thanks, >> Anjali. >> >
