[ 
https://issues.apache.org/jira/browse/FLINK-11482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bowen Li updated FLINK-11482:
-----------------------------
    Description: 
Implement catalog APIs for generic Flink metadata in HiveCatalog, since we 
unified {{GenericHiveMetastoreCatalog}} and {{HiveCatalog}} 

-{{GenericHiveMetastoreCatalog}} is a special implementation of 
{{ReadableWritableCatalog}} interface to store tables/views/functions defined 
in Flink to Hive metastore. With respect to the objects stored, 
{{GenericHiveMetastoreCatalog}} is similar to {{GenericInMemoryCatalog}}, but 
the storage used is a Hive metastore instead of memory.-

  was:{{GenericHiveMetastoreCatalog}} is a special implementation of 
{{ReadableWritableCatalog}} interface to store tables/views/functions defined 
in Flink to Hive metastore. With respect to the objects stored, 
{{GenericHiveMetastoreCatalog}} is similar to {{GenericInMemoryCatalog}}, but 
the storage used is a Hive metastore instead of memory.


> Implement catalog APIs for generic Flink metadata in HiveCatalog
> ----------------------------------------------------------------
>
>                 Key: FLINK-11482
>                 URL: https://issues.apache.org/jira/browse/FLINK-11482
>             Project: Flink
>          Issue Type: New Feature
>          Components: Connectors / Hive, Table SQL / API
>            Reporter: Xuefu Zhang
>            Assignee: Bowen Li
>            Priority: Major
>
> Implement catalog APIs for generic Flink metadata in HiveCatalog, since we 
> unified {{GenericHiveMetastoreCatalog}} and {{HiveCatalog}} 
> -{{GenericHiveMetastoreCatalog}} is a special implementation of 
> {{ReadableWritableCatalog}} interface to store tables/views/functions defined 
> in Flink to Hive metastore. With respect to the objects stored, 
> {{GenericHiveMetastoreCatalog}} is similar to {{GenericInMemoryCatalog}}, but 
> the storage used is a Hive metastore instead of memory.-



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to