[
https://issues.apache.org/jira/browse/FLINK-21643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21643:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor
pull-request-available (was: auto-deprioritized-major pull-request-available
stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> JDBC sink should be able to execute statements on multiple tables
> -----------------------------------------------------------------
>
> Key: FLINK-21643
> URL: https://issues.apache.org/jira/browse/FLINK-21643
> Project: Flink
> Issue Type: New Feature
> Components: Connectors / JDBC
> Reporter: Maciej Obuchowski
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> pull-request-available
>
> Currently datastream JDBC sink supports outputting data only to one table -
> by having to provide SQL template, from which SimpleBatchStatementExecutor
> creates PreparedStatement. Creating multiple sinks, each of which writes data
> to one table is impractical for moderate to large number of tables -
> relational databases don't usually tolerate large number of connections.
> I propose adding DynamicBatchStatementExecutor, which will additionally
> require
> 1) provided mechanism to create SQL statements based on given object
> 2) cache for prepared statements
> 3) mechanism for determining which statement should be used for given object
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
