Shawn-Hx opened a new pull request #13308:
URL: https://github.com/apache/flink/pull/13308


   
   ## What is the purpose of the change
   
   There are several invalid links in page 
https://ci.apache.org/projects/flink/flink-docs-release-1.11/zh/dev/table/common.html
   because of missing "<a>" tags or some other mistakes.
   
   ## Brief change log
   
   - Remove unnecessary prefix
       - line 300 `{{ site.baseurl 
}}/zh/dev/table/common.html#table-identifier-expanding` --> 
`#table-identifier-expanding`
   - Move "<a>" tag to right place
       - line 416 `<a name="table-identifier-expanding"></a>`
   - Add missing "<a>" tags
       - line 850 `<a name="integration-with-datastream-and-dataset-api"></a>`
       - line 1078 `<a name="mapping-of-data-types-to-table-schema"></a>`
   - Remove redundant prefix
       - line 1286 `{{ site.baseurl }}{% link dev/types_serialization.zh.md 
%}#pojos` --> `{% link dev/types_serialization.zh.md %}#pojos`
   
   ## Verifying this change
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   ## 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, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / **no** / 
don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## 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:
us...@infra.apache.org


Reply via email to