You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Huang Xingbo (Jira)" <ji...@apache.org> on 2021/01/30 05:52:00 UTC
[jira] [Commented] (FLINK-21202) Introduce TimeWindow and
CountWindow in PyFlink
[ https://issues.apache.org/jira/browse/FLINK-21202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275488#comment-17275488 ]
Huang Xingbo commented on FLINK-21202:
--------------------------------------
Hi [~wangpeibin] Why do you change the description? I don't think the description you added has much to do with this JIRA.
> Introduce TimeWindow and CountWindow in PyFlink
> -----------------------------------------------
>
> Key: FLINK-21202
> URL: https://issues.apache.org/jira/browse/FLINK-21202
> Project: Flink
> Issue Type: Sub-task
> Components: API / Python
> Affects Versions: 1.13.0
> Reporter: Huang Xingbo
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.13.0
>
>
> Now, when the lastrow function is used for de duplication, if two successive rows are equal, a fallback row and an update row will still be generated, which will trigger downstream repeated calculation.
> Therefore, by optimizing the logic of the deduplicatefunctionhelper, when the two rows before and after the fallback are equal, it can automatically offset, thus reducing the amount of calculation
> In order to reduce the impact on the existing logic, this change can be opened manually by adding a configuration item as a switch
--
This message was sent by Atlassian Jira
(v8.3.4#803005)