[
https://issues.apache.org/jira/browse/FLINK-21280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17374980#comment-17374980
]
Stephan Ewen commented on FLINK-21280:
--------------------------------------
I think the proper solution here is to allow the JDBC sink to work with object
reuse enabled. That limitation in the sink is also a problem for other sink
users, and should be easier to mitigate than requiring StateFun to work with a
different mode.
> Investigate a way to disable object reuse in StateFun
> -----------------------------------------------------
>
> Key: FLINK-21280
> URL: https://issues.apache.org/jira/browse/FLINK-21280
> Project: Flink
> Issue Type: Improvement
> Components: Stateful Functions
> Reporter: Igal Shilman
> Priority: Minor
>
> Currently in StateFun, we require object reuse to be enabled. We are doing it
> because Flink sources can emit arbitrary objects, but the first occurrence of
> the user defined payload serializer happens in a IngressRouterOperator. This
> works due to the fact that this operator is chained to the user, and with
> object reuse, the source output is passed as reference (without any Flink
> serialization) to the IngressRouterOperator.
> Unfortunately JdbcSink requires object reuse to be disabled, and therefore
> can't be used directly with StateFun.
> This issue was first reported on the mailing list:
> [http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Stateful-Functions-JDBC-Sink-Problems-td41265.html]
>
> This issue is about exploring a way to remove the object reuse requirement.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
