Fix auto_increment metric collection errors caused by using collation in INFORMATION_SCHEMA searches #833
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.
Hello, we have encountered the following issues in our actual production:
There are two tables in the database, test.x and test.X, which caused data collection failure.
Original error message:
The result set obtained from the original SQL query on the database is as follows:
MySQL instance parameters:
The data of the two tables with different cases, x and X, will appear twice separately. This caused the data collection to fail, and the relevant metrics for that node could not be collected. The table_schema and table_name need to be treated as case-sensitive unique keys for association.
References:
https://bugs.mysql.com/bug.php?id=34921
https://dev.mysql.com/doc/refman/5.7/en/charset-collation-information-schema.html