[CONJ-1142] Accessing INFORMATION_ SCHEMA STATISTICS reports a large number of checking permissions - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Done
Affects Version/s: None
Fix Version/s: 3.3.2
Component/s: metadata
Labels:
None

Description

SHOW FULL PROCESSLIST;

Id: 827
User: mysql
Host: 192.1.3.115:38378
db: dss
Command: Query
Time: 14
State: checking permissions
Info: SELECT A.TABLE_SCHEMA TABLE_CAT, NULL TABLE_SCHEM, A.TABLE_NAME, A.COLUMN_NAME, B.SEQ_IN_INDEX KEY_SEQ, B.INDEX_NAME PK_NAME FROM INFORMATION_SCHEMA.COLUMNS A, INFORMATION_SCHEMA.STATISTICS B WHERE A.COLUMN_KEY in ('PRI','pri') AND B.INDEX_NAME='PRIMARY' AND (A.TABLE_SCHEMA = 'ds') AND (B.TABLE_SCHEMA = 'ds') AND A.TABLE_NAME LIKE 'adm_history' AND B.TABLE_NAME LIKE 'adm_history' AND A.TABLE_SCHEMA = B.TABLE_SCHEMA AND A.TABLE_NAME = B.TABLE_NAME AND A.COLUMN_NAME = B.COLUMN_NAME ORDER BY A.COLUMN_NAME
Progress: 0.000

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

my.ini
2 kB
2023-11-30 09:00

Issue Links

is caused by

CONJ-1129 Metadata getPrimaryKeys using like in place of strict equality

Closed

Activity

Ascending order - Click to sort in descending order

kennyliao created issue - 2023-11-30 09:00

kennyliao made changes - 2023-11-30 09:03

Field	Original Value	New Value
Description	************************* 68. row *********************** Id: 827 User: mysql Host: 192.168.3.115:38378 db: dss Command: Query Time: 14 State: checking permissions Info: SELECT A.TABLE_SCHEMA TABLE_CAT, NULL TABLE_SCHEM, A.TABLE_NAME, A.COLUMN_NAME, B.SEQ_IN_INDEX KEY_SEQ, B.INDEX_NAME PK_NAME FROM INFORMATION_SCHEMA.COLUMNS A, INFORMATION_SCHEMA.STATISTICS B WHERE A.COLUMN_KEY in ('PRI','pri') AND B.INDEX_NAME='PRIMARY' AND (A.TABLE_SCHEMA = 'dss') AND (B.TABLE_SCHEMA = 'dss') AND A.TABLE_NAME LIKE 'adm_va_vehicle_feature_history' AND B.TABLE_NAME LIKE 'adm_history' AND A.TABLE_SCHEMA = B.TABLE_SCHEMA AND A.TABLE_NAME = B.TABLE_NAME AND A.COLUMN_NAME = B.COLUMN_NAME ORDER BY A.COLUMN_NAME Progress: 0.000 *********************** 69. row *************************	SHOW FULL PROCESSLIST; Id: 827 User: mysql Host: 192.168.3.115:38378 db: dss Command: Query Time: 14 State: checking permissions Info: SELECT A.TABLE_SCHEMA TABLE_CAT, NULL TABLE_SCHEM, A.TABLE_NAME, A.COLUMN_NAME, B.SEQ_IN_INDEX KEY_SEQ, B.INDEX_NAME PK_NAME FROM INFORMATION_SCHEMA.COLUMNS A, INFORMATION_SCHEMA.STATISTICS B WHERE A.COLUMN_KEY in ('PRI','pri') AND B.INDEX_NAME='PRIMARY' AND (A.TABLE_SCHEMA = 'dss') AND (B.TABLE_SCHEMA = 'dss') AND A.TABLE_NAME LIKE 'adm_va_vehicle_feature_history' AND B.TABLE_NAME LIKE 'adm_history' AND A.TABLE_SCHEMA = B.TABLE_SCHEMA AND A.TABLE_NAME = B.TABLE_NAME AND A.COLUMN_NAME = B.COLUMN_NAME ORDER BY A.COLUMN_NAME Progress: 0.000

Vladislav Vaintroub added a comment - 2023-11-30 13:49

I guess you need to provide (anonymized) DDL for all tables in the database.
Or other way to reproduce.

Vladislav Vaintroub added a comment - 2023-11-30 13:49 I guess you need to provide (anonymized) DDL for all tables in the database. Or other way to reproduce.

kennyliao made changes - 2023-12-01 00:46

Description

SHOW FULL PROCESSLIST;

      Id: 827
    User: mysql
    Host: 192.168.3.115:38378
      db: dss
Command: Query
    Time: 14
   State: checking permissions
    Info: SELECT A.TABLE_SCHEMA TABLE_CAT, NULL TABLE_SCHEM, A.TABLE_NAME, A.COLUMN_NAME, B.SEQ_IN_INDEX KEY_SEQ, B.INDEX_NAME PK_NAME FROM INFORMATION_SCHEMA.COLUMNS A, INFORMATION_SCHEMA.STATISTICS B WHERE A.COLUMN_KEY in ('PRI','pri') AND B.INDEX_NAME='PRIMARY' AND (A.TABLE_SCHEMA = 'dss') AND (B.TABLE_SCHEMA = 'dss') AND A.TABLE_NAME LIKE 'adm_va_vehicle_feature_history' AND B.TABLE_NAME LIKE 'adm_history' AND A.TABLE_SCHEMA = B.TABLE_SCHEMA AND A.TABLE_NAME = B.TABLE_NAME AND A.COLUMN_NAME = B.COLUMN_NAME ORDER BY A.COLUMN_NAME
Progress: 0.000

After running MySQL, there are 7 servers executing concurrently initially access information_schema， There are a large number of checking permissions in the schema, which takes a long time. There are 3200 files underdatabase ds

SHOW FULL PROCESSLIST;

Id: 827
User: mysql
Host: 192.1.3.115:38378
db: dss
Command: Query
Time: 14
State: checking permissions
Info: SELECT A.TABLE_SCHEMA TABLE_CAT, NULL TABLE_SCHEM, A.TABLE_NAME, A.COLUMN_NAME, B.SEQ_IN_INDEX KEY_SEQ, B.INDEX_NAME PK_NAME FROM INFORMATION_SCHEMA.COLUMNS A, INFORMATION_SCHEMA.STATISTICS B WHERE A.COLUMN_KEY in ('PRI','pri') AND B.INDEX_NAME='PRIMARY' AND (A.TABLE_SCHEMA = 'ds') AND (B.TABLE_SCHEMA = 'ds') AND A.TABLE_NAME LIKE 'adm_history' AND B.TABLE_NAME LIKE 'adm_history' AND A.TABLE_SCHEMA = B.TABLE_SCHEMA AND A.TABLE_NAME = B.TABLE_NAME AND A.COLUMN_NAME = B.COLUMN_NAME ORDER BY A.COLUMN_NAME
Progress: 0.000

kennyliao added a comment - 2023-12-01 00:51 - edited

This situation is bound to occur every time the mysqld is restarted，and There are a large number of sub tables in the database ds.

The environment built is a center with 6 distributed nodes, capturing slow queries for more than 0.2 seconds. None of the center nodes are present (Center Server first run), while the other 6 distributed nodes are all very slow(Concurrent Access Center Server).

Can we avoid it by optimizing what parameters? Or can upgrading the mariadb version solve this problem?

CREATE TABLE `adm_history` (
`ID` bigint(20) NOT NULL AUTO_INCREMENT ,
`CHANNEL_ID` varchar(50) NOT NULL ,
`CAPTURE_TIME` bigint(20) NOT NULL,
`PLATE_IMAGE_URL` varchar(200) DEFAULT NULL ,
`VEHICLE_URL` varchar(200) DEFAULT '' ,
`PICTURE_URL` varchar(200) DEFAULT NULL,
`FEATURE_VECTOR` blob DEFAULT NULL ,
`FEATURE_VERSION` varchar(64) DEFAULT NULL ,
`CODE` varchar(50) DEFAULT NULL ,
PRIMARY KEY (`ID`),
KEY `IDX_VEHICLE_FEATURE_TIME` (`CAPTURE_TIME`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin

CREATE TABLE `c_pic` (
`ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT ,
`DEV_ID` varchar(50) NOT NULL ,
`DEV_CHNNUM` int(11) NOT NULL,
`DEV_NAME` varchar(50) NOT NULL ,
`DEV_CHNNAME` varchar(50) NOT NULL ,
`CAR_NUM` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL ,
`EXT_CAR_NUM` varchar(100) DEFAULT NULL,
`CAR_NUM_LENGTH` varchar(100) DEFAULT NULL,
`CAR_NUM_AREA_CODE` varchar(100) DEFAULT NULL ,
`ISSUE_PLACE` varchar(100) DEFAULT NULL,
`CAR_NUMTYPE` int(11) NOT NULL ,
`CAR_NUMCOLOR` int(11) NOT NULL ,
`CAR_SPEED` int(11) DEFAULT NULL ,
`CAR_TYPE` int(11) NOT NULL ,
`CAR_COLOR` int(11) NOT NULL ,
`CAR_LENGTH` int(11) NOT NULL ,
`CAR_DIRECT` varchar(8) NOT NULL ,
`CAR_WAY_CODE` varchar(8) NOT NULL ,
`CAP_TIME` int(11) DEFAULT NULL ,
`CAP_DATE` datetime NOT NULL ,
`INF_NOTE` varchar(255) DEFAULT NULL ,
`MAX_SPEED` int(11) DEFAULT NULL ,
`MIN_SPEED` int(11) DEFAULT NULL ,
`CAR_IMG_URL` varchar(255) DEFAULT NULL ,
`CAR_IMG1_URL` varchar(255) DEFAULT NULL,
`CAR_IMG2_URL` varchar(255) DEFAULT NULL ,
`CAR_IMG3_URL` varchar(255) DEFAULT NULL ,
`CAR_IMG4_URL` varchar(255) DEFAULT NULL ,
`CAR_IMG5_URL` varchar(255) DEFAULT NULL ,
`REC_STAT` tinyint(4) DEFAULT 0 ,
`DEV_CHNID` varchar(50) NOT NULL ,
`CAR_IMG_COUNT` int(11) DEFAULT NULL ,
`SAVE_FLAG` tinyint(4) DEFAULT 0 ,
`DC_CLEANFLAG` tinyint(4) DEFAULT 0 ,
`PIC_ID` int(11) DEFAULT NULL ,
`CAR_IMG_PLATE_TOP` int(11) DEFAULT NULL ,
`CAR_IMG_PLATE_LEFT` int(11) DEFAULT NULL ,
`CAR_IMG_PLATE_BOTTOM` int(11) DEFAULT NULL ,
`CAR_IMG_PLATE_RIGHT` int(11) DEFAULT NULL,
`CAR_BRAND` int(11) DEFAULT NULL ,
`ISSAFETYBELT` tinyint(4) DEFAULT 0 ,
`ISVISOR` tinyint(4) DEFAULT 0 ,
`BIND_STAT` tinyint(4) DEFAULT 0 ,
`CAR_NUM_PIC` varchar(255) DEFAULT NULL ,
`COMBINED_PIC_URL` varchar(255) DEFAULT NULL ,
`VERIFY_MEMO` varchar(255) DEFAULT NULL ,
`CAR_WIDTH` int(11) DEFAULT NULL ,
`CAR_HEIGHT` int(11) DEFAULT NULL ,
`SERVICE_CODE` varchar(20) NOT NULL DEFAULT '0'
`REC_TYPE` int(11) DEFAULT NULL,
`PIC_RECORD_IDX` varchar(60) DEFAULT NULL,
`CROSSROAD_ID` varchar(30) DEFAULT NULL,
`CHAN_CODE` varchar(30) DEFAULT NULL,
`DATA_SOURCE` tinyint(4) DEFAULT NULL ,
`CREATE_TIME` timestamp NOT NULL DEFAULT current_timestamp() ,
`REC_CODE` varchar(32) DEFAULT NULL ,
`VIDEO_URL` varchar(255) DEFAULT NULL,
`CAP_DAY` date DEFAULT NULL ,
`CAP_DATE_UTC` bigint(20) DEFAULT NULL ,
`IN_VEHICLE_GROUP` tinyint(2) NOT NULL DEFAULT 0,
PRIMARY KEY (`ID`),
KEY `IDX_CP_COMBINE_UTC` (`CAR_NUM`,`CAP_DATE_UTC`),
KEY `IDX_PICRECORD_DEVCHNID_UTC` (`DEV_CHNID`,`CAP_DATE_UTC`),
KEY `IDX_CP_CAP_DATE_UTC` (`CAP_DATE_UTC`),
KEY `IDX_CPIC_BRAND_CD_UTC` (`CAR_BRAND`,`CAP_DATE_UTC`),
KEY `IDX_CPIC_BRAND_COLOR_UTC` (`CAR_BRAND`,`CAR_COLOR`,`CAP_DATE_UTC`),
KEY `IDX_CPIC_BRAND_DEV` (`CAR_BRAND`,`DEV_CHNID`),
KEY `IDX_CPIC_BRAND_COLOR_DEV` (`CAR_BRAND`,`CAR_COLOR`,`DEV_CHNID`),
KEY `IDX_CPIC_COLOR_DEV_UTC` (`CAR_COLOR`,`DEV_CHNID`,`CAP_DATE_UTC`),
KEY `IDX_CAR_TYPE_CAP_DATE_UTC` (`CAR_TYPE`,`CAP_DATE_UTC`),
KEY `IDX_IN_GROUP_CAP_DATE_UTC` (`IN_VEHICLE_GROUP`,`CAP_DATE_UTC`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin

kennyliao added a comment - 2023-12-01 00:51 - edited This situation is bound to occur every time the mysqld is restarted，and There are a large number of sub tables in the database ds. The environment built is a center with 6 distributed nodes, capturing slow queries for more than 0.2 seconds. None of the center nodes are present (Center Server first run), while the other 6 distributed nodes are all very slow(Concurrent Access Center Server). Can we avoid it by optimizing what parameters? Or can upgrading the mariadb version solve this problem? CREATE TABLE `adm_history` ( `ID` bigint(20) NOT NULL AUTO_INCREMENT , `CHANNEL_ID` varchar(50) NOT NULL , `CAPTURE_TIME` bigint(20) NOT NULL, `PLATE_IMAGE_URL` varchar(200) DEFAULT NULL , `VEHICLE_URL` varchar(200) DEFAULT '' , `PICTURE_URL` varchar(200) DEFAULT NULL, `FEATURE_VECTOR` blob DEFAULT NULL , `FEATURE_VERSION` varchar(64) DEFAULT NULL , `CODE` varchar(50) DEFAULT NULL , PRIMARY KEY (`ID`), KEY `IDX_VEHICLE_FEATURE_TIME` (`CAPTURE_TIME`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin CREATE TABLE `c_pic` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT , `DEV_ID` varchar(50) NOT NULL , `DEV_CHNNUM` int(11) NOT NULL, `DEV_NAME` varchar(50) NOT NULL , `DEV_CHNNAME` varchar(50) NOT NULL , `CAR_NUM` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL , `EXT_CAR_NUM` varchar(100) DEFAULT NULL, `CAR_NUM_LENGTH` varchar(100) DEFAULT NULL, `CAR_NUM_AREA_CODE` varchar(100) DEFAULT NULL , `ISSUE_PLACE` varchar(100) DEFAULT NULL, `CAR_NUMTYPE` int(11) NOT NULL , `CAR_NUMCOLOR` int(11) NOT NULL , `CAR_SPEED` int(11) DEFAULT NULL , `CAR_TYPE` int(11) NOT NULL , `CAR_COLOR` int(11) NOT NULL , `CAR_LENGTH` int(11) NOT NULL , `CAR_DIRECT` varchar(8) NOT NULL , `CAR_WAY_CODE` varchar(8) NOT NULL , `CAP_TIME` int(11) DEFAULT NULL , `CAP_DATE` datetime NOT NULL , `INF_NOTE` varchar(255) DEFAULT NULL , `MAX_SPEED` int(11) DEFAULT NULL , `MIN_SPEED` int(11) DEFAULT NULL , `CAR_IMG_URL` varchar(255) DEFAULT NULL , `CAR_IMG1_URL` varchar(255) DEFAULT NULL, `CAR_IMG2_URL` varchar(255) DEFAULT NULL , `CAR_IMG3_URL` varchar(255) DEFAULT NULL , `CAR_IMG4_URL` varchar(255) DEFAULT NULL , `CAR_IMG5_URL` varchar(255) DEFAULT NULL , `REC_STAT` tinyint(4) DEFAULT 0 , `DEV_CHNID` varchar(50) NOT NULL , `CAR_IMG_COUNT` int(11) DEFAULT NULL , `SAVE_FLAG` tinyint(4) DEFAULT 0 , `DC_CLEANFLAG` tinyint(4) DEFAULT 0 , `PIC_ID` int(11) DEFAULT NULL , `CAR_IMG_PLATE_TOP` int(11) DEFAULT NULL , `CAR_IMG_PLATE_LEFT` int(11) DEFAULT NULL , `CAR_IMG_PLATE_BOTTOM` int(11) DEFAULT NULL , `CAR_IMG_PLATE_RIGHT` int(11) DEFAULT NULL, `CAR_BRAND` int(11) DEFAULT NULL , `ISSAFETYBELT` tinyint(4) DEFAULT 0 , `ISVISOR` tinyint(4) DEFAULT 0 , `BIND_STAT` tinyint(4) DEFAULT 0 , `CAR_NUM_PIC` varchar(255) DEFAULT NULL , `COMBINED_PIC_URL` varchar(255) DEFAULT NULL , `VERIFY_MEMO` varchar(255) DEFAULT NULL , `CAR_WIDTH` int(11) DEFAULT NULL , `CAR_HEIGHT` int(11) DEFAULT NULL , `SERVICE_CODE` varchar(20) NOT NULL DEFAULT '0' `REC_TYPE` int(11) DEFAULT NULL, `PIC_RECORD_IDX` varchar(60) DEFAULT NULL, `CROSSROAD_ID` varchar(30) DEFAULT NULL, `CHAN_CODE` varchar(30) DEFAULT NULL, `DATA_SOURCE` tinyint(4) DEFAULT NULL , `CREATE_TIME` timestamp NOT NULL DEFAULT current_timestamp() , `REC_CODE` varchar(32) DEFAULT NULL , `VIDEO_URL` varchar(255) DEFAULT NULL, `CAP_DAY` date DEFAULT NULL , `CAP_DATE_UTC` bigint(20) DEFAULT NULL , `IN_VEHICLE_GROUP` tinyint(2) NOT NULL DEFAULT 0, PRIMARY KEY (`ID`), KEY `IDX_CP_COMBINE_UTC` (`CAR_NUM`,`CAP_DATE_UTC`), KEY `IDX_PICRECORD_DEVCHNID_UTC` (`DEV_CHNID`,`CAP_DATE_UTC`), KEY `IDX_CP_CAP_DATE_UTC` (`CAP_DATE_UTC`), KEY `IDX_CPIC_BRAND_CD_UTC` (`CAR_BRAND`,`CAP_DATE_UTC`), KEY `IDX_CPIC_BRAND_COLOR_UTC` (`CAR_BRAND`,`CAR_COLOR`,`CAP_DATE_UTC`), KEY `IDX_CPIC_BRAND_DEV` (`CAR_BRAND`,`DEV_CHNID`), KEY `IDX_CPIC_BRAND_COLOR_DEV` (`CAR_BRAND`,`CAR_COLOR`,`DEV_CHNID`), KEY `IDX_CPIC_COLOR_DEV_UTC` (`CAR_COLOR`,`DEV_CHNID`,`CAP_DATE_UTC`), KEY `IDX_CAR_TYPE_CAP_DATE_UTC` (`CAR_TYPE`,`CAP_DATE_UTC`), KEY `IDX_IN_GROUP_CAP_DATE_UTC` (`IN_VEHICLE_GROUP`,`CAP_DATE_UTC`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin

kennyliao made changes - 2023-12-01 07:37

Comment

[ After running MySQL, there are 7 servers executing concurrently initially access information_schema， There are a large number of checking permissions in the schema, which takes a long time. There are 3200 files underdatabase ds

SHOW FULL PROCESSLIST;

Id: 827
User: mysql
Host: 192.1.3.115:38378
db: dss
Command: Query
Time: 14
State: checking permissions
Info: SELECT A.TABLE_SCHEMA TABLE_CAT, NULL TABLE_SCHEM, A.TABLE_NAME, A.COLUMN_NAME, B.SEQ_IN_INDEX KEY_SEQ, B.INDEX_NAME PK_NAME FROM INFORMATION_SCHEMA.COLUMNS A, INFORMATION_SCHEMA.STATISTICS B WHERE A.COLUMN_KEY in ('PRI','pri') AND B.INDEX_NAME='PRIMARY' AND (A.TABLE_SCHEMA = 'ds') AND (B.TABLE_SCHEMA = 'ds') AND A.TABLE_NAME LIKE 'adm_history' AND B.TABLE_NAME LIKE 'adm_history' AND A.TABLE_SCHEMA = B.TABLE_SCHEMA AND A.TABLE_NAME = B.TABLE_NAME AND A.COLUMN_NAME = B.COLUMN_NAME ORDER BY A.COLUMN_NAME
Progress: 0.000 ]

Vladislav Vaintroub added a comment - 2023-12-01 09:12

kennyliao, is this query coming from MariaDB's JDBC driver? DatabaseMetadata.getPrimaryKeys()?

Can you execute it yourself, replacing

A.TABLE_NAME LIKE 'adm_history' AND B.TABLE_NAME LIKE 'adm_history' with
A.TABLE_NAME = 'adm_history' AND B.TABLE_NAME = 'adm_history'

(basically replacing LIKE with '=')
and then see if it helps?

I believe there is a bug in JDBC driver logic, documentation indicates there should not be wildcard search here, so no "LIKE". It possibly has an implication on how many tables are checked (and you got many)

Vladislav Vaintroub added a comment - 2023-12-01 09:12 kennyliao , is this query coming from MariaDB's JDBC driver? DatabaseMetadata.getPrimaryKeys()? Can you execute it yourself, replacing A.TABLE_NAME LIKE 'adm_history' AND B.TABLE_NAME LIKE 'adm_history' with A.TABLE_NAME = 'adm_history' AND B.TABLE_NAME = 'adm_history' (basically replacing LIKE with '=') and then see if it helps? I believe there is a bug in JDBC driver logic, documentation indicates there should not be wildcard search here, so no "LIKE". It possibly has an implication on how many tables are checked (and you got many)

Diego Dupin made changes - 2023-12-01 12:50

Link

This issue relates to ~~CONJ-1129~~ [ ~~CONJ-1129~~ ]

kennyliao added a comment - 2023-12-02 08:39 - edited

Vladislav Vaintroub，after ‘like’ replace to ‘=’ ，The distributed nodes has been shortened from 5 minutes to 2 minutes, and the effect is very obvious.

kennyliao added a comment - 2023-12-02 08:39 - edited Vladislav Vaintroub，after ‘like’ replace to ‘=’ ，The distributed nodes has been shortened from 5 minutes to 2 minutes, and the effect is very obvious.

Diego Dupin added a comment - 2023-12-02 13:25 - edited

kennyliao There was indeed a problem in mariadb connector. After discussing it with wlad, consist of 2 parts:

query has been corrected to use "=" in place of "like" following JDBC spec
DatabaseMetaData.getPrimaryKeys now use only IS.STATISTICS table

(correction done connector side in ~~CONJ-1129~~)

benchmark result show huge improvement: 12251.3 operations per second in place of 11.5 in testing environment, using 10k tables

Correction is for now only as a snapshot version for testing, until 3.3.2 release.
Snapshot can be used adding snapshot repository:

<repositories>

	<repository>

		<id>sonatype-nexus-snapshots</id>

		<name>Sonatype Nexus Snapshots</name>

		<url>https://oss.sonatype.org/content/repositories/snapshots</url>

	</repository>

</repositories>

<dependencies>

	<dependency>

		<groupId>org.mariadb.jdbc</groupId>

		<artifactId>mariadb-java-client</artifactId>

		<version>3.3.2-SNAPSHOT</version>

	</dependency>

</dependencies>

Diego Dupin added a comment - 2023-12-02 13:25 - edited kennyliao There was indeed a problem in mariadb connector. After discussing it with wlad , consist of 2 parts: query has been corrected to use "=" in place of "like" following JDBC spec DatabaseMetaData.getPrimaryKeys now use only IS.STATISTICS table (correction done connector side in CONJ-1129 ) benchmark result show huge improvement: 12251.3 operations per second in place of 11.5 in testing environment, using 10k tables Correction is for now only as a snapshot version for testing, until 3.3.2 release. Snapshot can be used adding snapshot repository: <repositories> <repository> <id>sonatype-nexus-snapshots</id> <name>Sonatype Nexus Snapshots</name> <url>https: //oss.sonatype.org/content/repositories/snapshots</url> </repository> </repositories> <dependencies> <dependency> <groupId>org.mariadb.jdbc</groupId> <artifactId>mariadb-java-client</artifactId> <version> 3.3 . 2 -SNAPSHOT</version> </dependency> </dependencies>

Vladislav Vaintroub made changes - 2023-12-12 14:42

Component/s		metadata [ 14002 ]
Component/s	Platform Windows [ 10138 ]
Key	~~MDEV-32915~~	~~CONJ-1142~~
Affects Version/s	10.5.17 [ 27509 ]
Project	MariaDB Server [ 10000 ]	MariaDB Connector/J [ 10301 ]

Vladislav Vaintroub added a comment - 2023-12-12 14:44 - edited

I moved it to Connector/J , as the fix is done inside the connector. I do not know about the blocker, only that it worked like this for a long time, or even since inception of the Connector. It is likely that only not very usual setups with many thousands of tables are affected

Vladislav Vaintroub added a comment - 2023-12-12 14:44 - edited I moved it to Connector/J , as the fix is done inside the connector. I do not know about the blocker, only that it worked like this for a long time, or even since inception of the Connector. It is likely that only not very usual setups with many thousands of tables are affected

Diego Dupin made changes - 2023-12-12 14:46

Priority

Blocker [ 1 ]

Major [ 3 ]

Diego Dupin made changes - 2023-12-12 14:47

Link

This issue is caused by ~~CONJ-1129~~ [ ~~CONJ-1129~~ ]

Diego Dupin made changes - 2023-12-12 14:47

Link

This issue relates to ~~CONJ-1129~~ [ ~~CONJ-1129~~ ]

Diego Dupin made changes - 2023-12-12 14:47

Fix Version/s		3.3.2 [ 29602 ]
Assignee		Diego Dupin [ diego dupin ]
Resolution		Done [ 10200 ]
Status	Open [ 1 ]	Closed [ 6 ]

Vladislav Vaintroub added a comment - 2023-12-22 00:07

That was released some days ago in Connector/J 3.3.2 ( https://mariadb.com/kb/en/mariadb-connector-j-3-3-2-release-notes/ )

Vladislav Vaintroub added a comment - 2023-12-22 00:07 That was released some days ago in Connector/J 3.3.2 ( https://mariadb.com/kb/en/mariadb-connector-j-3-3-2-release-notes/ )

People

Assignee:: Diego Dupin

Reporter:: kennyliao

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2023-11-30 09:00

Updated:: 2023-12-22 00:07

Resolved:: 2023-12-12 14:47

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Connector/J

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates

Git Integration