[
https://issues.apache.org/jira/browse/FLINK-21367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21367:
-----------------------------------
Labels: auto-unassigned pull-request-available stale-major (was:
auto-unassigned 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
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Support objectReuse in JDBC sink
> --------------------------------
>
> Key: FLINK-21367
> URL: https://issues.apache.org/jira/browse/FLINK-21367
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / JDBC
> Reporter: Roman Khachatryan
> Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-major
>
> Currently, if object reuse is enabled then JDBC sink factories will throw an
> exception. This prevents some use cases including recent one with Stateful
> Functions [1].
> To overcome this, JdbcBatchingOutputFormat can implement
> InputTypeConfigurable and use the obtained serializer to copy the record if
> object reuse is enabled.
> [1]
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Stateful-Functions-JDBC-Sink-Problems-td41265.html
>
> cc: [~igal], [~jark]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
