We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Since this commit : 8018fce
And the integration of the patch provided by @Wohlie we identified an issue on a client running MySQL 8.
The indexing process became suddenly very slow (from 2h to 20h) after upgrading Elasticsuite.
It seems that the query generated by the patch is problematic on MySQL 8.
Here is the explain on the client server :
For unknown reasons, it seems that it will use the index on "STORE_ID".
Here is the explain on another client server running MariaDB :
Here it uses the index on ATTRIBUTE_ID.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Since this commit : 8018fce
And the integration of the patch provided by @Wohlie we identified an issue on a client running MySQL 8.
The indexing process became suddenly very slow (from 2h to 20h) after upgrading Elasticsuite.
It seems that the query generated by the patch is problematic on MySQL 8.
Here is the explain on the client server :
For unknown reasons, it seems that it will use the index on "STORE_ID".
Here is the explain on another client server running MariaDB :
Here it uses the index on ATTRIBUTE_ID.
The text was updated successfully, but these errors were encountered: