You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2018/04/17 15:31:00 UTC
[jira] [Commented] (FLINK-9193) Deprecate non-well-defined output
methods on DataStream
[ https://issues.apache.org/jira/browse/FLINK-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441023#comment-16441023 ]
Timo Walther commented on FLINK-9193:
-------------------------------------
Do we really want to deprecate these useful methods? I think this will a big barrier especially for new users. Of course they have no well-defined semantics, but are useful for debugging, prototyping, and testing. Not every user needs strong consistency guarantees either.
> Deprecate non-well-defined output methods on DataStream
> -------------------------------------------------------
>
> Key: FLINK-9193
> URL: https://issues.apache.org/jira/browse/FLINK-9193
> Project: Flink
> Issue Type: Improvement
> Components: DataStream API
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
> Priority: Major
> Fix For: 1.5.0
>
>
> Some output methods on {{DataStream}} that write text to files are not safe to use in a streaming program as they have no consistency guarantees. They are:
> - {{writeAsText()}}
> - {{writeAsCsv()}}
> - {{writeToSocket()}}
> - {{writeUsingOutputFormat()}}
> Along with those we should also deprecate the {{SinkFunctions}} that they use.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)