You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Kostas Kloudas (JIRA)" <ji...@apache.org> on 2018/04/17 14:41:00 UTC

[jira] [Commented] (FLINK-9192) Undo parameterization of StateMachine Example

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

Kostas Kloudas commented on FLINK-9192:
---------------------------------------

These changes were made in the context of the end-to-end test for High Availability.

It was an intermediate step until the general purpose testing job is written, which will replace the StateMachine job in the test.

That said, I am totally up for undoing the changes.

> Undo parameterization of StateMachine Example
> ---------------------------------------------
>
>                 Key: FLINK-9192
>                 URL: https://issues.apache.org/jira/browse/FLINK-9192
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Stephan Ewen
>            Priority: Major
>
> The example has been changed to add parametrization and a different sink.
> I would vote to undo these changes, the make the example less nice and use non-recommended sinks:
>   - For state backend, incremental checkpoints, async checkpoints, etc. having these settings in the example blows up the parameter list of the example and distracts from what the example is about.
>   - If the main reason for this is an end-to-end test, then these settings should go into the test's Flink config.
>   - The {{writeAsText}} is a sink that is not recommended to use, because it is not integrated with checkpoints and has no well defined semantics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)