[
https://issues.apache.org/jira/browse/FLINK-21367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384255#comment-17384255
]
Roman Khachatryan edited comment on FLINK-21367 at 7/20/21, 1:32 PM:
---------------------------------------------------------------------
Merged as
d502353acd03428b9befa4ec970191b757b6c8c3..ef78c2e3df7a60024b643f9a9e057f95f7e40ba7.
was (Author: roman_khachatryan):
Merged as
5df9cb1d9d0d82910254b7dc89850e62b1ecfbb1..454c7dedcb15f742a5ebb097a38144e371fe55fc.
> 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: Critical
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> 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)
