You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/04/07 10:44:00 UTC

[jira] [Updated] (FLINK-21643) JDBC sink should be able to execute statements on multiple tables

     [ 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 pull-request-available stale-minor  (was: auto-deprioritized-major pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> 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: Minor
>              Labels: auto-deprioritized-major, pull-request-available, stale-minor
>
> 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)