-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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.
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
Bug Report: No schema found for table in vstreamer for tables with TABLESPACE innodb_system #12669
Comments
kovyrin
added
Needs Triage
This issue needs to be correctly labelled and triaged
Type: Bug
labels
Mar 20, 2023
mattlord
added
Component: Query Serving
and removed
Needs Triage
This issue needs to be correctly labelled and triaged
labels
Mar 20, 2023
4 tasks
kovyrin
added a commit
to kovyrin/vitess
that referenced
this issue
Mar 20, 2023
…m are not skipped when loading the schema (fixes vitessio#12669) Signed-off-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com>
I believe #12672 should fix the issue. |
frouioui
pushed a commit
that referenced
this issue
Mar 27, 2023
…m are included in the schema (#12672) * Use a left join to make sure that tables with tablespace=innodb_system are not skipped when loading the schema (fixes #12669) Signed-off-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com> * Set tablespace on a test table to see if it breaks vstreamer Signed-off-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com> --------- Signed-off-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com>
vitess-bot bot
pushed a commit
that referenced
this issue
Mar 27, 2023
…m are not skipped when loading the schema (fixes #12669) Signed-off-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com>
vitess-bot bot
pushed a commit
that referenced
this issue
Mar 27, 2023
…m are not skipped when loading the schema (fixes #12669) Signed-off-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com>
frouioui
pushed a commit
that referenced
this issue
Mar 28, 2023
…ce=innodb_system are included in the schema (#12672) (#12734) * Use a left join to make sure that tables with tablespace=innodb_system are not skipped when loading the schema (fixes #12669) Signed-off-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com> * Set tablespace on a test table to see if it breaks vstreamer Signed-off-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com> --------- Signed-off-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com> Co-authored-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com>
frouioui
pushed a commit
that referenced
this issue
Mar 28, 2023
…ce=innodb_system are included in the schema (#12672) (#12735) * Use a left join to make sure that tables with tablespace=innodb_system are not skipped when loading the schema (fixes #12669) Signed-off-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com> * Set tablespace on a test table to see if it breaks vstreamer Signed-off-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com> --------- Signed-off-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com> Co-authored-by: Oleksiy Kovyrin <oleksiy.kovyrin@shopify.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview of the Issue
When a table is created in Vitess with a
TABLESPACE innodb_system
option (as a result of https://bugs.mysql.com/bug.php?id=110383 or for some other reason) and Vitess is running on a MySQL 8.0 cluster, it leads to vstreamer failing with an unexpected "No schema found for table" error.This is caused by the fact, that the schema engine code relies on a query to information schema that joins
tables
withinnodb_tablespaces
using aRIGHT JOIN
to get a list of tables in a given database, while mysql does not provide tablespace information for tables within theinnodb_system
tablespace. This leads to all tables with theTABLESPACE innodb_system
option being filtered out from the result set. Later, when vstreamer uses the schema engine to get table information, it blows up failing to find the table.Interestingly enough, the 5.7 query uses a LEFT JOIN, so it does not suffer from the same issue.
Reproduction Steps
Binary Version
Tried it on a custom-built 14.0.0, but the issue exists in main as well.
Operating System and Environment details
The text was updated successfully, but these errors were encountered: