Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add info about compatibility issues with Connector/J 8.0 with TiDB v7.5 #15794

Merged
merged 4 commits into from
Dec 22, 2023
Merged

Add info about compatibility issues with Connector/J 8.0 with TiDB v7.5 #15794

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
bb38aca
Add info about compatibility issues with Connector/J 8.0 with TiDB v7…
dveeden Dec 19, 2023
2e085dc
Update develop/dev-guide-choose-driver-or-orm.md
dveeden Dec 20, 2023
6654bcf
make ci happy
Oreoxmt Dec 20, 2023
af656ef
refine wording
Oreoxmt Dec 20, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions develop/dev-guide-choose-driver-or-orm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,10 @@ You can follow the [MySQL documentation](https://dev.mysql.com/doc/connector-j/e
>
> There is a [bug](https://bugs.mysql.com/bug.php?id=106252) in the Connector/J 8.0 versions before 8.0.32, which might cause threads to hang when using TiDB versions earlier than v6.3.0. To avoid this issue, it is recommended that you use either MySQL Connector/J 8.0.32 or a later version, or the TiDB JDBC (see the *TiDB-JDBC* tab).

> **Note:**
>
> When using MySQL Connector/J 8.0 with TiDB v7.5.0 it is recommended to set [`server-version`](/tidb-configuration-file.md#server-version) in the configuration file for TiDB to "5.7.25-TiDB-v7.5.0" as MySQL Connector/J tries to use the `information_schema.KEYWORDS` table if the server announces a MySQL version that is 8.0.11 or newer and this table isn't present in TiDB v7.5.0. This is not needed with TiDB v7.6.0 and newer as that version comes with an `information_schema.KEYWORDS` table. This is also not needed with TiDB v7.4.0 and earlier as those versions identify themselves as MySQL 5.7.
dveeden marked this conversation as resolved.
Show resolved Hide resolved

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dveeden, please help confirm whether pingcap/tidb#48807 will be cherry-picked to v7.5. If yes, the above change looks okay because the issue will be fixed for v7.5.1.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is currently not clear if this will be backported or not. I'm discussing this with various people.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. If it is not backported in v7.5.1, we'll also need to include v7.5.1 in this note when v7.5.1 is published.

For an example of how to build a complete application, see [Build a simple CRUD app with TiDB and JDBC](/develop/dev-guide-sample-application-java-jdbc.md).

</div>
Expand Down
Loading