You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2017/06/29 22:19:00 UTC

[jira] [Closed] (FLINK-7025) Using NullByteKeySelector for Unbounded ProcTime NonPartitioned Over

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

Fabian Hueske closed FLINK-7025.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.2
                   1.4.0

Fixed for 1.3.2 with db7f0ffd4f882cdcb294c470a15665752b765816
Fixed for 1.4.0 with 55ab34ff3b92b2567bcab80f39826a9667f1c9ce

> Using NullByteKeySelector for Unbounded ProcTime NonPartitioned Over
> --------------------------------------------------------------------
>
>                 Key: FLINK-7025
>                 URL: https://issues.apache.org/jira/browse/FLINK-7025
>             Project: Flink
>          Issue Type: Bug
>          Components: Table API & SQL
>    Affects Versions: 1.3.1, 1.4.0
>            Reporter: sunjincheng
>            Assignee: sunjincheng
>             Fix For: 1.4.0, 1.3.2
>
>
> Currently we added `Cleanup State` feature. But It not work well if we enabled the stateCleaning on Unbounded ProcTime NonPartitioned Over window, Because in `ProcessFunctionWithCleanupState` we has using the keyed state.
> So, In this JIRA. I'll change the  `Unbounded ProcTime NonPartitioned Over` to `partitioned Over` by using NullByteKeySelector. OR created a `NonKeyedProcessFunctionWithCleanupState`. But I think the first way is simpler. What do you think? [~fhueske]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)