[ https://issues.apache.org/jira/browse/FLINK-11852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-11852: ----------------------------------- Labels: auto-deprioritized-minor auto-unassigned pull-request-available (was: auto-unassigned pull-request-available stale-minor) Priority: Not a Priority (was: Minor) This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > Improve Processing function example > ----------------------------------- > > Key: FLINK-11852 > URL: https://issues.apache.org/jira/browse/FLINK-11852 > Project: Flink > Issue Type: Improvement > Components: API / DataStream, Documentation > Affects Versions: 1.7.2 > Reporter: Flavio Pompermaier > Priority: Not a Priority > Labels: auto-deprioritized-minor, auto-unassigned, > pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > In the processing function documentation > ([https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/operators/process_function.html)] > there's an "abusive" usage of the timers since a new timer is registered for > every new tuple coming in. This could cause problems in terms of allocated > objects and could burden the overall application. > It could worth to mention this problem and remove useless timers, e.g.: > > {code:java} > CountWithTimestamp current = state.value(); > if (current == null) { > current = new CountWithTimestamp(); > current.key = value.f0; > } else { > ctx.timerService().deleteEventTimeTimer(current.lastModified + timeout); > }{code} > -- This message was sent by Atlassian Jira (v8.20.1#820001)