@PublicEvolving public final class ResolvedCatalogView extends Object implements ResolvedCatalogBaseTable<CatalogView>, CatalogView
CatalogView that is backed by the original metadata coming from the Catalog but resolved by the framework.CatalogBaseTable.TableKind| Constructor and Description |
|---|
ResolvedCatalogView(CatalogView origin,
ResolvedSchema resolvedSchema) |
| Modifier and Type | Method and Description |
|---|---|
CatalogBaseTable |
copy()
Get a deep copy of the CatalogBaseTable instance.
|
String |
getComment()
Get comment of the table or view.
|
Optional<String> |
getDescription()
Get a brief description of the table or view.
|
Optional<String> |
getDetailedDescription()
Get a detailed description of the table or view.
|
String |
getExpandedQuery()
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.
|
Map<String,String> |
getOptions()
Returns a map of string-based options.
|
CatalogView |
getOrigin()
Returns the original, unresolved metadata object from the
Catalog. |
String |
getOriginalQuery()
Original text of the view definition that also preserves the original formatting.
|
ResolvedSchema |
getResolvedSchema()
Returns a fully resolved and validated
ResolvedSchema. |
Schema |
getUnresolvedSchema()
Returns the schema of the table or view.
|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitgetSchemagetTableKind, ofpublic ResolvedCatalogView(CatalogView origin, ResolvedSchema resolvedSchema)
public CatalogView getOrigin()
ResolvedCatalogBaseTableCatalog.
This method might be useful if catalog-specific object instances should be directly forwarded from the catalog to a factory.
getOrigin in interface ResolvedCatalogBaseTable<CatalogView>public ResolvedSchema getResolvedSchema()
ResolvedCatalogBaseTableResolvedSchema.
Connectors can configure themselves by accessing ResolvedSchema.getPrimaryKey()
and ResolvedSchema.toPhysicalRowDataType().
getResolvedSchema in interface ResolvedCatalogBaseTable<CatalogView>public Map<String,String> getOptions()
CatalogBaseTableIn case of CatalogTable, these options may determine the kind of connector and its
configuration for accessing the data in the external system. See DynamicTableFactory
for more information. If a CatalogTable should not be serializable, an implementation
can simply throw a runtime exception in this method.
getOptions in interface CatalogBaseTablepublic Schema getUnresolvedSchema()
CatalogBaseTableThe schema can reference objects from other catalogs and will be resolved and validated by the framework when accessing the table or view.
getUnresolvedSchema in interface CatalogBaseTableResolvedCatalogTable,
ResolvedCatalogViewpublic String getComment()
CatalogBaseTablegetComment in interface CatalogBaseTablepublic CatalogBaseTable copy()
CatalogBaseTablecopy in interface CatalogBaseTablepublic Optional<String> getDescription()
CatalogBaseTablegetDescription in interface CatalogBaseTablepublic Optional<String> getDetailedDescription()
CatalogBaseTablegetDetailedDescription in interface CatalogBaseTablepublic String getOriginalQuery()
CatalogViewgetOriginalQuery in interface CatalogViewpublic String getExpandedQuery()
CatalogViewFor example, for a view that is defined in the context of "default" database with a query
select * from test1, the expanded query text might become select
`test1`.`name`, `test1`.`value` from `default`.`test1`, where table test1 resides in
database "default" and has two columns ("name" and "value").
getExpandedQuery in interface CatalogViewCopyright © 2014–2024 The Apache Software Foundation. All rights reserved.