[ 
https://issues.apache.org/jira/browse/FLINK-10556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669607#comment-16669607
 ] 

Bowen Li commented on FLINK-10556:
----------------------------------

sorry that I put the wrong jira number in one of my PRs and got linked here...

Thanks, Xuefu! The design doc looks very good to me! 

One small thing caught my eyes is external catalog's compatibility towards 
current YAML config file used by SQL Client, as mentioned in section 
`Additional Notes`. The parsing logic of YAML config file currently is on a 
different code path than catalog's, and the diverge will create maintenance 
issue. Providing a migration utility, as suggested in design doc, is one way to 
solve it, while we still need to maintain the utility tool. In the long run, 
I'd suggest unifying the code paths of YAML config file and catalog by 
developing something like a {{FlinkYamlCatalog}}. It will make both maintenance 
and migration a lot easier. What do you think?

> Integration with Apache Hive
> ----------------------------
>
>                 Key: FLINK-10556
>                 URL: https://issues.apache.org/jira/browse/FLINK-10556
>             Project: Flink
>          Issue Type: New Feature
>          Components: Batch Connectors and Input/Output Formats, SQL Client, 
> Table API & SQL
>    Affects Versions: 1.6.0
>            Reporter: Xuefu Zhang
>            Assignee: Xuefu Zhang
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: Flink-Hive Metastore Connectivity Design.pdf, Proposal_ 
> Integrate Flink with Hive Ecosystem.pdf
>
>
> This is an umbrella JIRA tracking all enhancement and issues related to 
> integrating Flink with Hive ecosystem. This is an outcome of a discussion in 
> the community, and thanks go to everyone that provided feedback and interest.
> Specifically, we'd like to see the following features and capabilities 
> immediately in Flink:
> # Metadata interoperability
> # Data interoperability
> # Data type compatibility
> # Hive UDF support
> # DDL/DML/Query language compatibility
> For a longer term, we'd also like to add or improve:
> # Compatible SQL service, client tools, JDBC/ODBC drivers
> # Better task failure tolerance and task scheduling
> # Support other user customizations in Hive (storage handlers, serdes, etc).
> I will provide more details regarding the proposal in a doc shortly. Design 
> doc, if deemed necessary, will be provided in each related sub tasks under 
> this JIRA.
> Feedback and contributions are greatly welcome!



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

Reply via email to