[
https://issues.apache.org/jira/browse/FLINK-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Nowojski updated FLINK-7497:
----------------------------------
Description:
Currently when using TwoPhaseCommitSinkFunction there is no way to store on
state additional user information that should be coupled with opened
transactions (like shared state between transaction).
It is required by FlinkKafkaProducer011, because there we need some place to
store a pool of used transactional.ids.
was:
Currently when using TwoPhaseCommitSinkFunction, if there is some intermittent
failure in "beginTransaction", not only the snapshot that triggered this call
fail, but also any subsequent write requests will fail also, rendering such
sink unusable until application restart.
This issue is in code that hasn't been released yet.
Issue Type: New Feature (was: Bug)
> Allow users to add custom user context stored in state in
> TwoPhaseCommitSinkFunction
> ------------------------------------------------------------------------------------
>
> Key: FLINK-7497
> URL: https://issues.apache.org/jira/browse/FLINK-7497
> Project: Flink
> Issue Type: New Feature
> Components: Streaming
> Affects Versions: 1.4.0
> Reporter: Piotr Nowojski
> Assignee: Piotr Nowojski
> Fix For: 1.4.0
>
>
> Currently when using TwoPhaseCommitSinkFunction there is no way to store on
> state additional user information that should be coupled with opened
> transactions (like shared state between transaction).
> It is required by FlinkKafkaProducer011, because there we need some place to
> store a pool of used transactional.ids.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
