Class ResolvedCatalogView
- All Implemented Interfaces:
CatalogBaseTable,CatalogView,ResolvedCatalogBaseTable<CatalogView>
CatalogView that is backed by the original metadata coming from the Catalog but resolved by the framework.-
Nested Class Summary
Nested classes/interfaces inherited from interface org.apache.flink.table.catalog.CatalogBaseTable
CatalogBaseTable.TableKind -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptioncopy()Get a deep copy of the CatalogBaseTable instance.Get comment of the table or view.Get a brief description of the table or view.Get a detailed description of the table or view.Expanded text of the original view definition This is needed because the context such as current DB is lost after the session, in which view is defined, is gone.Returns a map of string-based options.Returns the original, unresolved metadata object from theCatalog.Original text of the view definition that also preserves the original formatting.Returns a fully resolved and validatedResolvedSchema.Returns the schema of the table or view.Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface org.apache.flink.table.catalog.CatalogView
getTableKindMethods inherited from interface org.apache.flink.table.catalog.ResolvedCatalogBaseTable
getSchema
-
Constructor Details
-
ResolvedCatalogView
-
-
Method Details
-
getOrigin
Description copied from interface:ResolvedCatalogBaseTableReturns the original, unresolved metadata object from theCatalog.This method might be useful if catalog-specific object instances should be directly forwarded from the catalog to a factory.
- Specified by:
getOriginin interfaceResolvedCatalogBaseTable<CatalogView>
-
getResolvedSchema
Description copied from interface:ResolvedCatalogBaseTableReturns a fully resolved and validatedResolvedSchema.Connectors can configure themselves by accessing
ResolvedSchema.getPrimaryKey()andResolvedSchema.toPhysicalRowDataType().- Specified by:
getResolvedSchemain interfaceResolvedCatalogBaseTable<CatalogView>
-
getOptions
Description copied from interface:CatalogBaseTableReturns a map of string-based options.In case of
CatalogTable, these options may determine the kind of connector and its configuration for accessing the data in the external system. SeeDynamicTableFactoryfor more information. If aCatalogTableshould not be serializable, an implementation can simply throw a runtime exception in this method.- Specified by:
getOptionsin interfaceCatalogBaseTable
-
getUnresolvedSchema
Description copied from interface:CatalogBaseTableReturns the schema of the table or view.The schema can reference objects from other catalogs and will be resolved and validated by the framework when accessing the table or view.
- Specified by:
getUnresolvedSchemain interfaceCatalogBaseTable- See Also:
-
getComment
Description copied from interface:CatalogBaseTableGet comment of the table or view.- Specified by:
getCommentin interfaceCatalogBaseTable- Returns:
- comment of the table/view.
-
copy
Description copied from interface:CatalogBaseTableGet a deep copy of the CatalogBaseTable instance.- Specified by:
copyin interfaceCatalogBaseTable- Returns:
- a copy of the CatalogBaseTable instance
-
getDescription
Description copied from interface:CatalogBaseTableGet a brief description of the table or view.- Specified by:
getDescriptionin interfaceCatalogBaseTable- Returns:
- an optional short description of the table/view
-
getDetailedDescription
Description copied from interface:CatalogBaseTableGet a detailed description of the table or view.- Specified by:
getDetailedDescriptionin interfaceCatalogBaseTable- Returns:
- an optional long description of the table/view
-
getOriginalQuery
Description copied from interface:CatalogViewOriginal text of the view definition that also preserves the original formatting.- Specified by:
getOriginalQueryin interfaceCatalogView- Returns:
- the original string literal provided by the user.
-
getExpandedQuery
Description copied from interface:CatalogViewExpanded text of the original view definition This is needed because the context such as current DB is lost after the session, in which view is defined, is gone. Expanded query text takes care of this, as an example.For example, for a view that is defined in the context of "default" database with a query
select * from test1, the expanded query text might becomeselect `test1`.`name`, `test1`.`value` from `default`.`test1`, where table test1 resides in database "default" and has two columns ("name" and "value").- Specified by:
getExpandedQueryin interfaceCatalogView- Returns:
- the view definition in expanded text.
-