You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jark Wu (JIRA)" <ji...@apache.org> on 2019/07/03 09:50:00 UTC
[jira] [Closed] (FLINK-12977) Port CsvTableSource and CsvTableSink
to api-java-bridge
[ https://issues.apache.org/jira/browse/FLINK-12977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jark Wu closed FLINK-12977.
---------------------------
Resolution: Fixed
Assignee: Luo Gen
Fix Version/s: 1.9.0
Fixed in 1.9.0 with 2 commits:
Port CsvTableSink: 981a54d6718753ca5b2cd68259b72b4ecea9008a
Port CsvTableSource: 635cd554e94e2c87858785f7e1227aa804eedc5e
> Port CsvTableSource and CsvTableSink to api-java-bridge
> -------------------------------------------------------
>
> Key: FLINK-12977
> URL: https://issues.apache.org/jira/browse/FLINK-12977
> Project: Flink
> Issue Type: Task
> Components: Table SQL / API
> Reporter: Jark Wu
> Assignee: Luo Gen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, CsvTableSource and CsvTableSink are in flink-planner. If they can be moved to `flink-table-api-java-bridge`, so that blink planner can reuse them.
> This should be a straightforward move, no API should be changed. And we should rewrite them in Java, because {{api-java-bridge}} doesn't depends on Scala.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)