-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Make sure Yes/No attribute Layered Navigation filter uses index #21772
Conversation
Hi @stkec. Thank you for your contribution
For more details, please, review the Magento Contributor Assistant documentation |
Hi @VladimirZaets, thank you for the review. |
merge latest M2
QA passed. |
3e16afc
to
3c50c7c
Compare
Hi @stkec, thank you for your contribution! |
Fixes performance degradation when using Yes/No attributes in Layered navigation [#21771](Related Issue: #21771)
Description (*)
After #3283 merged it is possible to use Yes/No attributes in Layered Navigation. But when MySql engine assembles the SQL query there are 2 more places where FrontendInput of the Layered Navigation Attribute is hardcoded as ['select', 'multiselect']. As a result, Yes/No attribute processed not as a 'Term' condition as it suppose to be for Layered Attribute but as a default unknown condition
Fixed Issues (if relevant)
Manual testing scenarios (*)
Contribution checklist (*)