[docs] Translate mysql cdc doc to Chinese #1398
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…anslate_mysql-cdc-doc # Conflicts: # docs/content/connectors/mysql-cdc(ZH).md
leonardBang
reviewed
Jul 28, 2022
There was a problem hiding this comment.
Thanks @RookieGao for the great work, I left some comments.
|
|
||
| ### SQL Client JAR | ||
|
|
||
| ```下载链接仅适用于稳定版本。``` |
There was a problem hiding this comment.
下载链接仅在已发布版本可用，请在文档网站左下角选择浏览已发布的版本。
| MySQL CDC 连接器是一个 Flink Source 连接器，它将首先读取表快照块，然后继续读取 binlog， | ||
| 无论是在快照阶段还是读取 binlog 阶段，MySQL CDC 连接器都会在处理时**准确读取数据**，即使任务出现了故障。 | ||
|
|
||
| ### Startup Reading Position |
|
|
||
| **Note:** 请参考 [Deserialization](../about.html#deserialization) 有关 JSON 反序列化的更多详细信息。 | ||
|
|
||
| ### 扫描新添加的表 |
| ``` | ||
| **Note:** 请参考文档 [Restore the job from previous savepoint](https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/cli/#command-line-interface) 了解更多详细信息。 | ||
|
|
||
| Data Type Mapping |
|
I will modify it according to the suggestions. Thank you for your review. |
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
Co-authored-by: Leonard Xu <leonard@apache.org>
…o/flink-cdc-connectors into translate_mysql-cdc-doc rebase master
leonardBang
reviewed
Jul 29, 2022
| |-----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| | ||
| | [mysql-cdc](mysql-cdc.md) | <li> [MySQL](https://dev.mysql.com/doc): 5.6, 5.7, 8.0.x <li> [RDS MySQL](https://www.aliyun.com/product/rds/mysql): 5.6, 5.7, 8.0.x <li> [PolarDB MySQL](https://www.aliyun.com/product/polardb): 5.6, 5.7, 8.0.x <li> [Aurora MySQL](https://aws.amazon.com/cn/rds/aurora): 5.6, 5.7, 8.0.x <li> [MariaDB](https://mariadb.org): 10.x <li> [PolarDB X](https://github.com/ApsaraDB/galaxysql): 2.0.1 | JDBC Driver: 8.0.21 | | ||
|
|
||
| Dependencies |
| LONGBLOB<br> | ||
| </td> | ||
| <td>BYTES</td> | ||
| <td>Currently, for BLOB data type in MySQL, only the blob whose length isn't greater than 2,147,483,647(2 ** 31 - 1) is supported. </td> |
Comment on lines
785
to
812
| <td>The JSON data type will be converted into STRING with JSON format in Flink.</td> | ||
| </tr> | ||
| <tr> | ||
| <td> | ||
| SET | ||
| </td> | ||
| <td>ARRAY<STRING></td> | ||
| <td>As the SET data type in MySQL is a string object that can have zero or more values, | ||
| it should always be mapped to an array of string | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <td> | ||
| GEOMETRY<br> | ||
| POINT<br> | ||
| LINESTRING<br> | ||
| POLYGON<br> | ||
| MULTIPOINT<br> | ||
| MULTILINESTRING<br> | ||
| MULTIPOLYGON<br> | ||
| GEOMETRYCOLLECTION<br> | ||
| </td> | ||
| <td> | ||
| STRING | ||
| </td> | ||
| <td> | ||
| The spatial data types in MySQL will be converted into STRING with a fixed Json format. | ||
| Please see <a href="#空间数据类型映射 ">空间数据类型映射</a> section for more detailed information. |
Comment on lines
820
to
838
| The spatial data types except for `GEOMETRYCOLLECTION` in MySQL will be converted into Json String with a fixed format like:<br> | ||
| ```json | ||
| {"srid": 0 , "type": "xxx", "coordinates": [0, 0]} | ||
| ``` | ||
| The field `srid` identifies the SRS in which the geometry is defined, SRID 0 is the default for new geometry values if no SRID is specified. | ||
| As only MySQL 8+ support to specific SRID when define spatial data type, the field `srid` will always be 0 in MySQL with a lower version. | ||
|
|
||
| The field `type` identifies the spatial data type, such as `POINT`/`LINESTRING`/`POLYGON`. | ||
|
|
||
| The field `coordinates` represents the `coordinates` of the spatial data. | ||
|
|
||
| For `GEOMETRYCOLLECTION`, it will be converted into Json String with a fixed format like:<br> | ||
| ```json | ||
| {"srid": 0 , "type": "GeometryCollection", "geometries": [{"type":"Point","coordinates":[10,10]}]} | ||
| ``` | ||
|
|
||
| The field `geometries` is an array contains all spatial data. | ||
|
|
||
| The example for different spatial data types mapping is as follows: |
Co-authored-by: Leonard Xu <leonard@apache.org>
|
It is in rebase. After completion, it will be modified according to the suggestions |
added 2 commits
July 29, 2022 15:32
…o/flink-cdc-connectors into translate_mysql-cdc-doc megre
Co-authored-by: Leonard Xu <leonard@apache.org>
…anslate_mysql-cdc-doc
|
I made a mess... I want to open a PR again |
|
This PR content has been transferred to #1435 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR Main solutions #1391
There may be inaccuracies or omissions in the translation of the first edition.