You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2021/07/05 19:52:00 UTC
[jira] [Issue Comment Deleted] (FLINK-21280) Investigate a way to
disable object reuse in StateFun
[ https://issues.apache.org/jira/browse/FLINK-21280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen updated FLINK-21280:
---------------------------------
Comment: was deleted
(was: This issue was labeled "stale-major" 7 ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion.
)
> 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
> Labels: auto-deprioritized-major
>
> 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)