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-1322) Scala API does not respect WriteMode set by configuration
Date Fri, 12 Dec 2014 14:51:13 GMT

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

ASF GitHub Bot commented on FLINK-1322:

GitHub user aljoscha opened a pull request:


    [FLINK-1322] Make Scala API respect WriteMode set in Config


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/aljoscha/incubator-flink scala-write-overwrite

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #266
commit 844d8ed94608b236518b23d7085df63a8c92c578
Author: Aljoscha Krettek <aljoscha.krettek@gmail.com>
Date:   2014-12-12T14:48:19Z

    [FLINK-1322] Make Scala API respect WriteMode set in Config


> Scala API does not respect WriteMode set by configuration
> ---------------------------------------------------------
>                 Key: FLINK-1322
>                 URL: https://issues.apache.org/jira/browse/FLINK-1322
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Till Rohrmann
>            Assignee: Aljoscha Krettek
>            Priority: Minor
> The Scala API does not have output methods which do not take a WriteMode parameter. As
default value the NO_OVERWRITE is set. Consequently, a possible global WriteMode set in the
configuration is always overwritten. The Java API behaves differently, if no WriteMode is
provided. We should sync both APIs to guarantee consistent behaviour.

This message was sent by Atlassian JIRA

View raw message