You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/04/30 22:02:57 UTC

[GitHub] [flink] sjwiesman opened a new pull request #8326: Flink 12378

sjwiesman opened a new pull request #8326: Flink 12378
URL: https://github.com/apache/flink/pull/8326
 
 
   ## What is the purpose of the change
   
   
   
   Currently flink's filesystem documentation is spread across a number of pages without any clear connection. A non-exhaustive list of issues includes:
   
       S3 documentation spread across many pages
       OSS filesystem is listed under deployments when it is an object store
       deployments/filesystem.md has a lot of unrelated information
   
   We should create a filesystem subsection under deployments with multiple pages containing all relevant information about Flink's filesystem abstraction.
   
   This PR also resolves FLINK-8513 and FLINK-10249 which were minor additions to the S3 documentation. 
   
   ## Verifying this change
   N/A
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
     - The S3 file system connector: (**yes** / no / don't know)
   This does not touch S3 file system code but does touch the documentation. 
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (not applicable / **docs** / JavaDocs / not documented)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services