Thanks for working on this, John! I'd like to see a more complete write-up of what you're proposing. Without that, I don't think we can have a productive discussion about this.
For example, I think you're proposing to keep the view columns to ensure that the same columns are produced by the view every time, based on requirements from the SQL spec. Let's start by stating what those behavior requirements are, so that everyone has the context to understand why your proposal includes the view columns. Similarly, I'd like to know why you're proposing `softwareVersion` in the view definition. On Tue, Aug 13, 2019 at 8:56 AM John Zhuge <jzh...@apache.org> wrote: > Catalog support has been added to DSv2 along with a table catalog > interface. Here I'd like to propose a view catalog interface, for the > following benefit: > > - Abstraction for view management thus allowing different view backends > - Disassociation of view definition storage from Hive Metastore > > A catalog plugin can be both TableCatalog and ViewCatalog. Resolve an > identifier as view first then table. > > More details in SPIP and PR if we decide to proceed. Here is a quick > glance at the API: > > ViewCatalog interface: > > - loadView > - listViews > - createView > - deleteView > > View interface: > > - name > - originalSql > - defaultCatalog > - defaultNamespace > - viewColumns > - owner > - createTime > - softwareVersion > - options (map) > > ViewColumn interface: > > - name > - type > > > Thanks, > John Zhuge > -- Ryan Blue Software Engineer Netflix
