[ https://issues.apache.org/jira/browse/FLINK-10697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xuefu Zhang closed FLINK-10697. ------------------------------- Resolution: Duplicate Fix Version/s: (was: 1.8.0) > Create FlinkInMemoryCatalog class, an in-memory catalog that stores Flink's > meta objects for production use > ----------------------------------------------------------------------------------------------------------- > > Key: FLINK-10697 > URL: https://issues.apache.org/jira/browse/FLINK-10697 > Project: Flink > Issue Type: Sub-task > Components: Table API & SQL > Affects Versions: 1.6.1 > Reporter: Xuefu Zhang > Assignee: Bowen Li > Priority: Major > Labels: pull-request-available > > Currently all Flink meta objects (currently tables only) are stored in memory > as part of Calcite catalog. Those objects are temporary (such as inline > tables), others are meant to live beyond user session. As we introduce > catalog for those objects (tables, views, and UDFs), it makes sense to > organize them neatly. Further, having a catalog implementation that store > those objects in memory is to retain the currently behavior, which can be > configured by user. > Please note that this implementation is different from the current > {{InMemoryExternalCatalog}, which is used mainly for testing and doesn't > reflect what's actually needed for Flink meta objects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)