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

Till Rohrmann commented on FLINK-20341:
---------------------------------------

Very good point you are bringing up here [~Leonard Xu]. Sorry for messing the 
documentation up. 

Quick question because when building the documentation locally, I did not see 
the problem: Do we need to pass a special command to build the Chinese 
documentation or how does it happen that you don't have the 
{{deployment/config.md}} files?

As a general observation, having to maintain two sets of links manually is 
quite tedious given how many links we actually have in the documentation. Can 
this be automated?

> Rework Deployment / Coordination Documentation
> ----------------------------------------------
>
>                 Key: FLINK-20341
>                 URL: https://issues.apache.org/jira/browse/FLINK-20341
>             Project: Flink
>          Issue Type: Task
>          Components: Documentation, Runtime / Coordination
>            Reporter: Robert Metzger
>            Assignee: Robert Metzger
>            Priority: Major
>             Fix For: 1.12.0
>
>
> Problems:
> - Clusters & Deployment pages are very inhomogeneous
> - Overview page has good intentions, but is a huge wall of text
>  - Native K8s and YARN have a “Background / Internals” page
>  - difference between Local Cluster and Standalone Cluster is unclear
> Goals:
> - Deploying a Flink cluster is one of the first tasks when getting to know 
> Flink. We need proper guidance for making these steps a success
> - We need a proper separation between general concepts (HA, session/perjob 
> mode) and implementations of them (ZK HA, K8s HA, YARN session, …). Also 
> orthogonal aspects such as FileSystems, Plugins, Security etc.
> Related work:
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-42%3A+Rework+Flink+Documentation
>  (see “Deployment Section”)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to