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

Search Engine - Elasticsearch throws "mapper_parsing_exception" #21889

Closed
jaideepghosh opened this issue Mar 22, 2019 · 9 comments
Closed

Search Engine - Elasticsearch throws "mapper_parsing_exception" #21889

jaideepghosh opened this issue Mar 22, 2019 · 9 comments
Labels
Component: Elasticsearch Component: Search Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed

Comments

@jaideepghosh
Copy link
Member

Preconditions (*)

  1. Downloaded magento2.3.0 from magento.com and installed.
  2. Installed elasticsearch 6.4.2
  3. Configure Magento to use Elasticsearch. (Source)

Steps to reproduce (*)

  1. Configure Magento to use Elasticsearch. (Source)
  2. Execute php <your Magento install dir>/bin/magento indexer:reindex catalogsearch_fulltext as mentioned in Dev Docs

Expected result (*)

Screen Shot 2019-03-22 at 4 56 38 PM

Actual result (*)

Screen Shot 2019-03-22 at 4 57 50 PM

Catalog Search indexer process unknown error:
{"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"No handler for type [string] declared on field [category_ids]"}],"type":"mapper_parsing_exception","reason":"No handler for type [string] declared on field [category_ids]"},"status":400}

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Mar 22, 2019
@magento-engcom-team
Copy link
Contributor

magento-engcom-team commented Mar 22, 2019

Hi @jaideepghosh. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@jaideepghosh do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

  • yes
  • no

@jaideepghosh
Copy link
Member Author

@magento-engcom-team give me 2.3-develop instance

@magento-engcom-team
Copy link
Contributor

Hi @jaideepghosh. Thank you for your request. I'm working on Magento 2.3-develop instance for you

@magento-engcom-team
Copy link
Contributor

Hi @jaideepghosh, here is your Magento instance.
Admin access: https://i-21889-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

@jaideepghosh
Copy link
Member Author

@magento-engcom-team give me 2.3 instance

@jaideepghosh
Copy link
Member Author

I found an alternate solution for this issue, ie:

Implementation of elasticsearch 6.0 already on 2.3-develop branch and will be available on 2.3.1 release. #21458

@jaideepghosh
Copy link
Member Author

After switching to elasticsearch 5.4.2 from elasticsearch 6.4.2, Still getting the same error, ie:

{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Illegal dynamic template parameter: [match_mapping]"}],"type":"illegal_argument_exception","reason":"Illegal dynamic template parameter: [match_mapping]"},"status":400}

Here is my elasticsearch status:
Screen Shot 2019-03-22 at 6 56 33 PM

@jaideepghosh jaideepghosh reopened this Mar 22, 2019
@ghost ghost self-assigned this Mar 22, 2019
@magento-engcom-team
Copy link
Contributor

Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • Next steps are available in case you are a member of Community Maintainers.

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

@ghost
Copy link

ghost commented Mar 22, 2019

Hi @jaideepghosh thank you for your report, only elasticsearch 5.2.x supported not 5.x .https://devdocs.magento.com/guides/v2.3/config-guide/elasticsearch/es-overview.html
Magento Open Source 2.3.x supports the following Elasticsearch versions:

Elasticsearch 5.2
Elasticsearch 2.x

@ghost ghost closed this as completed Mar 22, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Elasticsearch Component: Search Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed
Projects
None yet
Development

No branches or pull requests

2 participants