[
https://issues.apache.org/jira/browse/FLINK-10769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674696#comment-16674696
]
ASF GitHub Bot commented on FLINK-10769:
----------------------------------------
bowenli86 commented on issue #7012: [FLINK-10769][Table & SQL] port
InMemoryExternalCatalog to java
URL: https://github.com/apache/flink/pull/7012#issuecomment-435762643
@twalthr @fhueske Can you please take a look?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> port InMemoryExternalCatalog to java
> ------------------------------------
>
> Key: FLINK-10769
> URL: https://issues.apache.org/jira/browse/FLINK-10769
> Project: Flink
> Issue Type: Sub-task
> Components: Table API & SQL
> Reporter: Bowen Li
> Assignee: Bowen Li
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
>
> In the Flink-Hive integration design, we propose a new FlinkInMemoryCatalog
> (FLINK-10697) for production use. FlinkInMemoryCatalog will share some part
> with the existing InMemoryExternalCatalog, thus we need to make changes to
> InMemoryExternalCatalog.
> As we are moving away from Scala to Java, we should write all new
> code/feature in Java. Therefore, we will port InMemoryExternalCatalog to java
> first without any feature or behavior change.
> This is a pre-requisite for FLINK-10697
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
