flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igal Shilman (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-21280) Investigate a way to disable object reuse in StateFun
Date Thu, 20 May 2021 09:15:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-21280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Igal Shilman updated FLINK-21280:
    Fix Version/s:     (was: statefun-3.1.0)

> 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: Major
>              Labels: stale-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

View raw message