flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4842) Introduce test to enforce order of operator / udf lifecycles
Date Mon, 17 Oct 2016 13:20:58 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15582242#comment-15582242

ASF GitHub Bot commented on FLINK-4842:

Github user StephanEwen commented on the issue:

    Thanks for adding this test. I think it would be good to extend it to cases where `write(byte[])`
is called as well. I would also use some more "odd" numbers for buffer size, so make sure
there is no case where it works if the "in mem threshold" is a multiple of the buffer size.
For example, user `17` as buffer size and `31` as memory-threshold.

> Introduce test to enforce order of operator / udf lifecycles 
> -------------------------------------------------------------
>                 Key: FLINK-4842
>                 URL: https://issues.apache.org/jira/browse/FLINK-4842
>             Project: Flink
>          Issue Type: Test
>            Reporter: Stefan Richter
>            Assignee: Stefan Richter
> We should introduce a test that enforces a certain order in which life cycle methods
of operators and udfs are called, so that they are not easily changed by accident.

This message was sent by Atlassian JIRA

View raw message