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

    https://github.com/apache/flink/pull/1524#discussion_r50252252
  
    --- Diff: docs/setup/config.md ---
    @@ -52,6 +52,14 @@ The configuration files for the TaskManagers can be 
different, Flink does not as
     - `parallelism.default`: The default parallelism to use for programs that 
have no parallelism specified. (DEFAULT: 1). For setups that have no concurrent 
jobs running, setting this value to NumTaskManagers * NumSlotsPerTaskManager 
will cause the system to use all available execution resources for the 
program's execution. **Note**: The default parallelism can be overwriten for an 
entire job by calling `setParallelism(int parallelism)` on the 
`ExecutionEnvironment` or by passing `-p <parallelism>` to the Flink 
Command-line frontend. It can be overwritten for single transformations by 
calling `setParallelism(int
     parallelism)` on an operator. See the [programming 
guide]({{site.baseurl}}/apis/programming_guide.html#parallel-execution) for 
more information about the parallelism.
     
    +- `fs.default-scheme`: The default filesystem scheme to be used, with the 
necessary authority (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. As another example, if this is set to 
`hdfs://localhost:9000/`, then a user-specified file path 
    +without explicit scheme definition, such as `/user/USERNAME/in.txt`, is 
going to be transformed into 
    +`hdfs://localhost:9000/user/USERNAME/in.txt`, and a HDFS deployment is 
going to be used with its NameNode 
    --- End diff --
    
    I would remove the last part after the comma: `, and a HDFS...port 9000`.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to