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

Allow user defined dropdown attributes to be searchable with Elasticsearch #18368

Closed
wants to merge 1 commit into from
Closed

Allow user defined dropdown attributes to be searchable with Elasticsearch #18368

wants to merge 1 commit into from

Conversation

luckyraul
Copy link

@luckyraul luckyraul commented Oct 3, 2018

In elasticsearch currently we have index created for drop-down attribute

"brand_value": "Nivea",
"brand": "38156"

Magento is searching with this request

            {
               "match":{
                  "brand":{
                     "query":"Nivea",
                     "boost":10
                  }
               }
            }

instead of

            {
               "match":{
                  "brand_value":{
                     "query":"Nivea",
                     "boost":10
                  }
               }
            }

If I update attribute to is_user_defined = 0, search request is correct.

@magento-cicd2
Copy link
Contributor

magento-cicd2 commented Oct 3, 2018

CLA assistant check
All committers have signed the CLA.

@rogyar
Copy link
Contributor

rogyar commented Oct 4, 2018

Hi @luckyraul. Please, provide the PR description according to the template so we can analyze the information and perform the proper testing steps. You can take a look at another PR for an example (#17968). Thank you

@luckyraul
Copy link
Author

@rogyar is it enough?

Copy link
Member

@sivaschenko sivaschenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any need in isUserDefined check here

@magento-engcom-team
Copy link
Contributor

Hi @sivaschenko, thank you for the review.
ENGCOM-3402 has been created to process this Pull Request

@magento-engcom-team
Copy link
Contributor

@luckyraul thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository.

@sivaschenko
Copy link
Member

@luckyraul can you please add steps to test the actual problem to help with the QA for this issue.

@sivaschenko
Copy link
Member

@luckyraul closing this pull request as the issue cannot be reproduced on the latest 2.3 Magento, looks like already fixed by the core team (https://github.com/magento/magento2/search?q=MAGETWO-94482&type=Commits). Please feel free to reopen and provide more details if you are able to reproduce the problem on the latest codebase.

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

Successfully merging this pull request may close these issues.

6 participants