You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "vinoyang (JIRA)" <ji...@apache.org> on 2018/09/10 15:24:00 UTC
[jira] [Assigned] (FLINK-10315) Let JDBCAppendTableSink be built
with java.sql.Connection
[ https://issues.apache.org/jira/browse/FLINK-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
vinoyang reassigned FLINK-10315:
--------------------------------
Assignee: vinoyang
> Let JDBCAppendTableSink be built with java.sql.Connection
> ---------------------------------------------------------
>
> Key: FLINK-10315
> URL: https://issues.apache.org/jira/browse/FLINK-10315
> Project: Flink
> Issue Type: Improvement
> Components: Java API
> Environment: I'm currently using Flink 1.6.0 Java.
> Reporter: François Lacombe
> Assignee: vinoyang
> Priority: Major
>
> Currently, JDBCAppendTableSink is built with methods like setDBUrl, setUsername, setPassword... and so on.
> We can't use an existing Java SQL connection to build it.
> It may be great to add a setConnection() method to the builder class as to prevent sensitive data like username or password to transit through large stacks from config connectors (often in main()) to JDBC sinks.
> To be able to provide only one object is far lighter than 4 or 5 strings
>
> Thanks in advance
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)