Bug #92142 | Having different result set with a full text index on different MySQL versions. | ||
---|---|---|---|
Submitted: | 23 Aug 2018 7:30 | Modified: | 24 Aug 2018 15:05 |
Reporter: | Chaitanya Tondlekar | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: FULLTEXT search | Severity: | S3 (Non-critical) |
Version: | 5.7.19 and 5.7.21 | OS: | Other (AWS RDS) |
Assigned to: | CPU Architecture: | Other | |
Tags: | full text search, utf8_bin collation, utf8_general_ci collation |
[23 Aug 2018 7:30]
Chaitanya Tondlekar
[24 Aug 2018 15:05]
MySQL Verification Team
Hi, I have ran your 100 % exact test case. With 5.7.19 I get this output: text_sample Telefe Channel1 text_sample Telefe SD Telefe Channel1 text_sample Telefé Channel1 Telefe Channel1 With 5.7.22 I get this output: text_sample Telefe SD Telefe Channel1 text_sample Telefé Channel1 Telefe Channel1 Verified as reported.
[17 Nov 2022 16:55]
Johannes Runkel
Any updates on this?
[18 Nov 2022 14:02]
MySQL Verification Team
Hi Mr. Tondlekar, Thank you for your interest. Nobody can reply to your question, because bug fixing scheduling is unknown, for both of the supported versions 5.7 and 8.0. Scheduling is done with each of the teams in charge of the category and version. Scheduling is kept only within those teams and changes all the time.
[18 Nov 2022 23:43]
Rick James
Still failing in 8.0.31