[
https://issues.apache.org/jira/browse/FLINK-19283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321361#comment-17321361
]
Flink Jira Bot commented on FLINK-19283:
----------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> Allow subclasses to override/extend FlinkKafkaConsumerBase checkpoint methods
> -----------------------------------------------------------------------------
>
> Key: FLINK-19283
> URL: https://issues.apache.org/jira/browse/FLINK-19283
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka
> Affects Versions: 1.11.0, 1.11.1
> Reporter: Adrian Kreuziger
> Priority: Minor
> Labels: stale-minor
>
> I'm working on a class that extends the FlinkKafkaConsumer to add some
> additional functionality the first time the consumer runs. I'd like to be
> able to store some additional state, but am unable to do so as the
> initializeState() and snapshotState() are marked as final. Ideally I'd like
> to be able to do something like
> {code:java}
> @Override
> public void initializeState(FunctionInitializationContext context) throws
> Exception {
> super.initializeState(context);
> // some additional initialization here
> }
> @Override
> public void snapshotState(FunctionSnapshotContext context) throws Exception {
> super.snapshotState(context);
> // set some additional state here
> }{code}
> I'm guessing it was marked final for a reason, is there a reason this would
> be problematic? The restoredState and unionOffsetStates properties are still
> private which would prevent subclasses from modifying the offset state.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
