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-8475) Move remaining sections to generated tables
Date Mon, 12 Feb 2018 16:24:00 GMT

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

ASF GitHub Bot commented on FLINK-8475:

Github user zentol commented on a diff in the pull request:

    --- Diff: flink-core/src/main/java/org/apache/flink/configuration/CoreOptions.java ---
    @@ -127,7 +130,30 @@
     	public static final ConfigOption<String> DEFAULT_FILESYSTEM_SCHEME = ConfigOptions
    -			.noDefaultValue();
    +			.noDefaultValue()
    +			.withDescription("The default filesystem scheme, used for paths that do not declare
a scheme explicitly.");
    --- End diff --
    ah I remember now, looking at the description:
    The default filesystem scheme to be used
    , with the necessary authority to contact, e.g. the host:port of the NameNode in the case
of HDFS (if needed).
    By default, this is set to file:/// which points to the local filesystem. This means that
the local filesystem is going to be used to search for user-specified files without an explicit
scheme definition.
    This scheme is used ONLY if no other scheme is specified (explicitly) in the user-provided
    Part 1 and 4 are contained in the description, part 3 was left out since file:/// isn't
the documented default. Only part 2 is really missing.

> Move remaining sections to generated tables
> -------------------------------------------
>                 Key: FLINK-8475
>                 URL: https://issues.apache.org/jira/browse/FLINK-8475
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Configuration
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>             Fix For: 1.5.0

This message was sent by Atlassian JIRA

View raw message