[
https://issues.apache.org/jira/browse/FLINK-38153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18086558#comment-18086558
]
Zhe Wang commented on FLINK-38153:
----------------------------------
Hi all,
I looked into this issue and would like to help if the approach sounds
reasonable.
What I observed:
- Both the zh and English release-2.0 JDBC DataStream docs currently render
this dependency:
`org.apache.flink:flink-connector-jdbc:4.0.0-2.0`.
- Maven Central metadata for `org.apache.flink:flink-connector-jdbc`
currently has latest/release `3.3.0-1.20` and does not list `4.0.0-2.0`.
- Maven Central metadata for `org.apache.flink:flink-connector-jdbc-core`
does list `4.0.0-2.0`.
- In `apache/flink-connector-jdbc` branch `v4.0`, `docs/data/jdbc.yml` points
to `flink-connector-jdbc-core` with `flink_compatibility: ['2.0']`, while the
DataStream docs use the `connector_artifact` shortcode.
- The relevant hotfix commit appears to be `433d165 [hotfix][docs] Use
flink-connector-jdbc-core for maven dependency (#165)`. It is contained by
`origin/v4.0` but not by tag `v4.0.0`; the tag's `docs/data/jdbc.yml` still
points to `flink-connector-jdbc`.
- The rendered release-2.0 page's "Edit This Page" link points to
`apache/flink/release-2.0`, but the raw source paths I checked returned 404, so
I am not fully sure which branch/repo should be changed or republished.
Likely cause:
- This looks like a docs artifactId/source-generation or release-docs
publishing issue rather than a runtime connector bug. It may be related to
release docs being generated from a source that does not include the `433d165`
docs metadata hotfix.
Proposed approach:
- If `flink-connector-jdbc-core` is the intended artifact for Flink 2.0
DataStream JDBC, update or republish the release-2.0 docs so the dependency
snippet uses `flink-connector-jdbc-core:4.0.0-2.0`.
- Could a committer confirm whether this should be fixed by republishing
release-2.0 docs from the `v4.0` branch metadata, backporting the metadata
hotfix, or changing another docs source?
Validation plan:
- Re-check both zh and English rendered dependency snippets.
- Re-check the Maven Central metadata/URLs for `flink-connector-jdbc` and
`flink-connector-jdbc-core`.
- Run the docs preview/build check once the correct source path is confirmed.
Does this direction make sense? If so, could a committer assign the ticket to
me?
Thanks,
Zhe Wang
> Documentation has an error
> ---------------------------
>
> Key: FLINK-38153
> URL: https://issues.apache.org/jira/browse/FLINK-38153
> Project: Flink
> Issue Type: Bug
> Components: Connectors / JDBC
> Reporter: Bao Liu
> Priority: Minor
>
> see
> [https://nightlies.apache.org/flink/flink-docs-release-2.0/zh/docs/connectors/datastream/jdbc/]
>
> {code:java}
> <dependency>
> <groupId>org.apache.flink</groupId>
> <artifactId>flink-connector-jdbc</artifactId>
> <version>4.0.0-2.0</version>
> </dependency> {code}
> In maven central
> [https://repo1.maven.org/maven2/org/apache/flink/flink-connector-jdbc/] , do
> not have this package.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
