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/28 08:04:00 UTC
[jira] [Commented] (FLINK-7025) Using NullByteKeySelector for
Unbounded ProcTime NonPartitioned Over
[ https://issues.apache.org/jira/browse/FLINK-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066101#comment-16066101 ]
Fabian Hueske commented on FLINK-7025:
--------------------------------------
I agree. IMO, we should go for the keyed state (NullByteKeySelector) approach. This will also be more consistent with the other Over window operators.
> Using NullByteKeySelector for Unbounded ProcTime NonPartitioned Over
> --------------------------------------------------------------------
>
> Key: FLINK-7025
> URL: https://issues.apache.org/jira/browse/FLINK-7025
> Project: Flink
> Issue Type: Bug
> Reporter: sunjincheng
> Assignee: sunjincheng
>
> 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)