flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flink Jira Bot (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-11852) Improve Processing function example
Date Thu, 27 May 2021 23:04:03 GMT

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

Flink Jira Bot updated FLINK-11852:
    Labels: pull-request-available stale-assigned  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community
manage its development. I see this issue is assigned but has not received an update in 14,
so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a comment updating
the community on your progress.  If this issue is waiting on feedback, please consider this
a reminder to the committer/reviewer. Flink is a very active project, and so we appreciate
your patience.
If you are no longer working on the issue, please unassign yourself so someone else may work
on it. If the "warning_label" label is not removed in 7 days, the issue will be automatically

> 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
>            Assignee: TANG Wen-hui
>            Priority: Minor
>              Labels: pull-request-available, stale-assigned
>          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

View raw message