[
https://issues.apache.org/jira/browse/FLINK-14395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952560#comment-16952560
]
vinoyang commented on FLINK-14395:
----------------------------------
[~jark] Actually, I am not familiar with the plan and context pf table/SQL. The
decision comes from [~aljoscha]. From the naming of two modules of connectors,
peoples can not see the purpose of what you described. It seems it is used to
distinguish between datastream connector and SQL connector. If the purpose is
like what you said, we need to revert for es7 connector. However, IMO, the
naming of "flink-sql-connector-xxx" is terrible.
> Refactor ES 6 connector to split table-specific code into
> flink-sql-connector-elasticsearch6
> --------------------------------------------------------------------------------------------
>
> Key: FLINK-14395
> URL: https://issues.apache.org/jira/browse/FLINK-14395
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / ElasticSearch
> Reporter: vinoyang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, for ES6 connector and ES6 SQL connector, table-specific code has a
> problem with improper placement. The relevant code should be moved from es6
> connector to es6 SQL connector.
> More details and contexts, please see:
> https://github.com/apache/flink/pull/9720#issuecomment-541996415
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
