Skip to content
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

[ Enhancement ] Automatically determine when a table should not use --innodb-optimize-keys #389

Closed
davidducos opened this issue Aug 5, 2021 · 2 comments · Fixed by #732 or #734
Closed

Comments

@davidducos
Copy link
Member

Currently --innodb-optimize-keys is applied to none or all the tables. We need to develop a formula to determine if it should be used per table basis.

@davidducos
Copy link
Member Author

We also need to discards the tables that has constraint with ON DELETE CASCADE ON UPDATE CASCADE or other options that makes impossible to execute the ALTER TABLE statements in another import stage.

@davidducos davidducos changed the title [ Enhancement ] Automatically determine when a table should use --innodb-optimize-keys [ Enhancement ] Automatically determine when a table should not use --innodb-optimize-keys Sep 29, 2021
@davidducos
Copy link
Member Author

We need to develop a (parametrized) formula to flag as unsuitable the small table based on amount of rows and indexes length.

Reference: https://www.percona.com/blog/2015/01/21/importing-big-tables-large-indexes-myloader/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment