You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently running Maxwell 1.39.3 to sync a MySQL8 instance to GCP PubSub.
We encountered issue when modifying some tables with json columns.
Maxwell schema parser seems to not like some index creation on JSON fields. It will crash with following error. ERROR SchemaChange - Error parsing SQL: 'ALTER TABLE tournaments ADD INDEX idx_team_name (('$.teams.name'))'
I don't see any SQL error in this request and it has been successfully processed by MySQL engine.
The text was updated successfully, but these errors were encountered:
ok i posted a patch, but i don't think that index isn't doing what you want -- that's literally just indexing the string '$.teams.name', you want something like:
add INDEX idx ((CAST(data->>"$.teams.name" AS CHAR(30)) COLLATE utf8mb4_bin))
- Bugfix issue where SQL query would go missing (#1973)
- Various parser bugfixes (#1970, #1982, #1987)
- Fix issue with renaming a primary key column (#1977)
We are currently running Maxwell 1.39.3 to sync a MySQL8 instance to GCP PubSub.
We encountered issue when modifying some tables with json columns.
Maxwell schema parser seems to not like some index creation on JSON fields. It will crash with following error.
ERROR SchemaChange - Error parsing SQL: 'ALTER TABLE tournaments ADD INDEX idx_team_name (('$.teams.name'))'
I don't see any SQL error in this request and it has been successfully processed by MySQL engine.
The text was updated successfully, but these errors were encountered: