sjwiesman edited a comment on issue #11885:
URL: https://github.com/apache/flink/pull/11885#issuecomment-618436232


   @alpinegizmo I found a number of broken links still within the docs. I'll 
fix these while merging. 
   
   ```
   http://localhost:4000/concepts/stream-processing.html:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/concepts/programming-model.html:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/concepts/runtime.html:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/internals/stream_checkpointing.html:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/zh/concepts/flink-architecture.html:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/dev/best_practices.html:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/ops/memory/config.html:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/zh/concepts/programming-model.html:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/zh/concepts/runtime.html:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/dev/dev/table/python/installation.html:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/fig/times_clocks.svg:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/zh/internals/stream_checkpointing.html:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/zh/dev/table/sql.html:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/zh/ops/memory/config.html:
   Remote file does not exist -- broken link!!!
   --
   http://localhost:4000/s3.zh.mdops/deployment/hadoop.html:
   Remote file does not exist -- broken link!!!
   ```


----------------------------------------------------------------
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:
[email protected]


Reply via email to