-
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
Adds Planning and Parsing Support for Create Index of MySQL 5.7 #7024
Adds Planning and Parsing Support for Create Index of MySQL 5.7 #7024
Conversation
Signed-off-by: GuptaManan100 <manan@planetscale.com>
Signed-off-by: GuptaManan100 <manan@planetscale.com>
Signed-off-by: GuptaManan100 <manan@planetscale.com>
Signed-off-by: GuptaManan100 <manan@planetscale.com>
Signed-off-by: GuptaManan100 <manan@planetscale.com>
Signed-off-by: GuptaManan100 <manan@planetscale.com>
Signed-off-by: GuptaManan100 <manan@planetscale.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look good. Unfortunately for me, I didn't consider CREATE INDEX
when parsing online DDL; while it's a valid query, I only planned for ALTER TABLE
. Moreover, gh-ost
only supports ALTER TABLE
form.
What I would like to consider is to have a func (*CreateIndex) ToAlterTable() *Statement
function. Given the fields in CreateIndex struct
I feel like this is reasonable to accomplish. What do you think?
Signed-off-by: GuptaManan100 <manan@planetscale.com>
Yes, we can have that function for converting |
Signed-off-by: GuptaManan100 <manan@planetscale.com>
sounds good! I'm happy to author that change myself. |
Signed-off-by: GuptaManan100 <manan@planetscale.com>
Signed-off-by: GuptaManan100 <manan@planetscale.com>
Signed-off-by: GuptaManan100 <manan@planetscale.com>
Signed-off-by: GuptaManan100 <manan@planetscale.com>
Signed-off-by: GuptaManan100 <manan@planetscale.com>
"Keyspace": { | ||
"Name": "user", | ||
"Sharded": true | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this not be main
keyspace?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see it is fixed in next commit.
Adds Planning and Parsing Support for Create Index of MySQL 5.7