Magento 2 Elasticsearch: Root mapping definition has unsupported












1















I am trying to setup elasticsearch 2.4.5 on a internal server and trying to use this for my EE 2.1.6 setup (magento installed in my local version). Following are the ES details.



{
"name" : "The Grip",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "TtY4Vl4LRJ22V5wF1fhkOQ",
"version" : {
"number" : "2.4.5",
"build_hash" : "c849dd13904f53e63e88efc33b2ceeda0b6a1276",
"build_timestamp" : "2017-04-24T16:18:17Z",
"build_snapshot" : false,
"lucene_version" : "5.5.4"
},
"tagline" : "You Know, for Search"
}


When I try reindexing I get the following error.



Catalog Search indexer process unknown error:
mapper_parsing_exception: Root mapping definition has unsupported parameters: [
from: 0
][
size: 10000
][
stored_fields: [
_id,
_score
]
][
query: {
bool={
should=[
{
match={
sku=shirt
}
},
{
match={
_all=shirt
}
},
{
match={
color=shirt
}
},
{
match={
description=shirt
}
},
{
match={
manufacturer=shirt
}
},
{
match={
name=shirt
}
},
{
match={
short_description=shirt
}
},
{
match={
status_value=shirt
}
},
{
match={
tax_class_id_value=shirt
}
}
],
minimum_should_match=1
}
}
][
aggregations: {
price_bucket={
extended_stats={
field=price_0_1
}
},
category_bucket={
terms={
field=category_ids
}
}
}
]


When I do it again then I get the following error.
Catalog Search indexer process unknown error:
illegal_argument_exception: Alias action [match] not supported



When I try using search on the store front it gives me an exception.



Exception #0 (ElasticsearchCommonExceptionsMissing404Exception): 
{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index","resource.type":"index_or_alias","resource.id":"magento2_product_1","index":"magento2_product_1"}],"type":"index_not_found_exception","reason":"no such index","resource.type":"index_or_alias","resource.id":"magento2_product_1","index":"magento2_product_1"},"status":404}


The above exception makes sense as Magento is looking for index magento2_product_1 and in ES the index created is magento2_product_1_v1.



Does anyone know what the error is really about? Why Magento is not able to create the index fully.










share|improve this question
















bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • First make sure that the Elasticsearch supports Magento EE version 2.1.x. From their documentation, If you get the Elasticsearch software from the Elasticsearch Linux repository, we support versions 2.x. If you get the Elasticsearch software from their Elasticsearch-PHP repository, we support the 2.0 branch.

    – Elavarasan
    Jun 13 '17 at 7:27













  • @Elavarasan - I have followed the docs provided by Magento on the Devdocs. Unless they haven't updated the doc for the newer Magneto version or if something is missing on my end it should be working fine as per the configurations we have in the Devdocs.

    – VK Ranjith
    Jun 13 '17 at 14:57













  • have try to in reindexing?

    – Ajay Patel
    Jul 26 '18 at 10:10
















1















I am trying to setup elasticsearch 2.4.5 on a internal server and trying to use this for my EE 2.1.6 setup (magento installed in my local version). Following are the ES details.



{
"name" : "The Grip",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "TtY4Vl4LRJ22V5wF1fhkOQ",
"version" : {
"number" : "2.4.5",
"build_hash" : "c849dd13904f53e63e88efc33b2ceeda0b6a1276",
"build_timestamp" : "2017-04-24T16:18:17Z",
"build_snapshot" : false,
"lucene_version" : "5.5.4"
},
"tagline" : "You Know, for Search"
}


When I try reindexing I get the following error.



Catalog Search indexer process unknown error:
mapper_parsing_exception: Root mapping definition has unsupported parameters: [
from: 0
][
size: 10000
][
stored_fields: [
_id,
_score
]
][
query: {
bool={
should=[
{
match={
sku=shirt
}
},
{
match={
_all=shirt
}
},
{
match={
color=shirt
}
},
{
match={
description=shirt
}
},
{
match={
manufacturer=shirt
}
},
{
match={
name=shirt
}
},
{
match={
short_description=shirt
}
},
{
match={
status_value=shirt
}
},
{
match={
tax_class_id_value=shirt
}
}
],
minimum_should_match=1
}
}
][
aggregations: {
price_bucket={
extended_stats={
field=price_0_1
}
},
category_bucket={
terms={
field=category_ids
}
}
}
]


When I do it again then I get the following error.
Catalog Search indexer process unknown error:
illegal_argument_exception: Alias action [match] not supported



When I try using search on the store front it gives me an exception.



Exception #0 (ElasticsearchCommonExceptionsMissing404Exception): 
{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index","resource.type":"index_or_alias","resource.id":"magento2_product_1","index":"magento2_product_1"}],"type":"index_not_found_exception","reason":"no such index","resource.type":"index_or_alias","resource.id":"magento2_product_1","index":"magento2_product_1"},"status":404}


The above exception makes sense as Magento is looking for index magento2_product_1 and in ES the index created is magento2_product_1_v1.



Does anyone know what the error is really about? Why Magento is not able to create the index fully.










share|improve this question
















bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • First make sure that the Elasticsearch supports Magento EE version 2.1.x. From their documentation, If you get the Elasticsearch software from the Elasticsearch Linux repository, we support versions 2.x. If you get the Elasticsearch software from their Elasticsearch-PHP repository, we support the 2.0 branch.

    – Elavarasan
    Jun 13 '17 at 7:27













  • @Elavarasan - I have followed the docs provided by Magento on the Devdocs. Unless they haven't updated the doc for the newer Magneto version or if something is missing on my end it should be working fine as per the configurations we have in the Devdocs.

    – VK Ranjith
    Jun 13 '17 at 14:57













  • have try to in reindexing?

    – Ajay Patel
    Jul 26 '18 at 10:10














1












1








1








I am trying to setup elasticsearch 2.4.5 on a internal server and trying to use this for my EE 2.1.6 setup (magento installed in my local version). Following are the ES details.



{
"name" : "The Grip",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "TtY4Vl4LRJ22V5wF1fhkOQ",
"version" : {
"number" : "2.4.5",
"build_hash" : "c849dd13904f53e63e88efc33b2ceeda0b6a1276",
"build_timestamp" : "2017-04-24T16:18:17Z",
"build_snapshot" : false,
"lucene_version" : "5.5.4"
},
"tagline" : "You Know, for Search"
}


When I try reindexing I get the following error.



Catalog Search indexer process unknown error:
mapper_parsing_exception: Root mapping definition has unsupported parameters: [
from: 0
][
size: 10000
][
stored_fields: [
_id,
_score
]
][
query: {
bool={
should=[
{
match={
sku=shirt
}
},
{
match={
_all=shirt
}
},
{
match={
color=shirt
}
},
{
match={
description=shirt
}
},
{
match={
manufacturer=shirt
}
},
{
match={
name=shirt
}
},
{
match={
short_description=shirt
}
},
{
match={
status_value=shirt
}
},
{
match={
tax_class_id_value=shirt
}
}
],
minimum_should_match=1
}
}
][
aggregations: {
price_bucket={
extended_stats={
field=price_0_1
}
},
category_bucket={
terms={
field=category_ids
}
}
}
]


When I do it again then I get the following error.
Catalog Search indexer process unknown error:
illegal_argument_exception: Alias action [match] not supported



When I try using search on the store front it gives me an exception.



Exception #0 (ElasticsearchCommonExceptionsMissing404Exception): 
{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index","resource.type":"index_or_alias","resource.id":"magento2_product_1","index":"magento2_product_1"}],"type":"index_not_found_exception","reason":"no such index","resource.type":"index_or_alias","resource.id":"magento2_product_1","index":"magento2_product_1"},"status":404}


The above exception makes sense as Magento is looking for index magento2_product_1 and in ES the index created is magento2_product_1_v1.



Does anyone know what the error is really about? Why Magento is not able to create the index fully.










share|improve this question
















I am trying to setup elasticsearch 2.4.5 on a internal server and trying to use this for my EE 2.1.6 setup (magento installed in my local version). Following are the ES details.



{
"name" : "The Grip",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "TtY4Vl4LRJ22V5wF1fhkOQ",
"version" : {
"number" : "2.4.5",
"build_hash" : "c849dd13904f53e63e88efc33b2ceeda0b6a1276",
"build_timestamp" : "2017-04-24T16:18:17Z",
"build_snapshot" : false,
"lucene_version" : "5.5.4"
},
"tagline" : "You Know, for Search"
}


When I try reindexing I get the following error.



Catalog Search indexer process unknown error:
mapper_parsing_exception: Root mapping definition has unsupported parameters: [
from: 0
][
size: 10000
][
stored_fields: [
_id,
_score
]
][
query: {
bool={
should=[
{
match={
sku=shirt
}
},
{
match={
_all=shirt
}
},
{
match={
color=shirt
}
},
{
match={
description=shirt
}
},
{
match={
manufacturer=shirt
}
},
{
match={
name=shirt
}
},
{
match={
short_description=shirt
}
},
{
match={
status_value=shirt
}
},
{
match={
tax_class_id_value=shirt
}
}
],
minimum_should_match=1
}
}
][
aggregations: {
price_bucket={
extended_stats={
field=price_0_1
}
},
category_bucket={
terms={
field=category_ids
}
}
}
]


When I do it again then I get the following error.
Catalog Search indexer process unknown error:
illegal_argument_exception: Alias action [match] not supported



When I try using search on the store front it gives me an exception.



Exception #0 (ElasticsearchCommonExceptionsMissing404Exception): 
{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index","resource.type":"index_or_alias","resource.id":"magento2_product_1","index":"magento2_product_1"}],"type":"index_not_found_exception","reason":"no such index","resource.type":"index_or_alias","resource.id":"magento2_product_1","index":"magento2_product_1"},"status":404}


The above exception makes sense as Magento is looking for index magento2_product_1 and in ES the index created is magento2_product_1_v1.



Does anyone know what the error is really about? Why Magento is not able to create the index fully.







magento2 magento-2.1 catalogsearch magento2.1.6






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 19 '17 at 14:57







VK Ranjith

















asked Jun 9 '17 at 13:29









VK RanjithVK Ranjith

577




577





bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • First make sure that the Elasticsearch supports Magento EE version 2.1.x. From their documentation, If you get the Elasticsearch software from the Elasticsearch Linux repository, we support versions 2.x. If you get the Elasticsearch software from their Elasticsearch-PHP repository, we support the 2.0 branch.

    – Elavarasan
    Jun 13 '17 at 7:27













  • @Elavarasan - I have followed the docs provided by Magento on the Devdocs. Unless they haven't updated the doc for the newer Magneto version or if something is missing on my end it should be working fine as per the configurations we have in the Devdocs.

    – VK Ranjith
    Jun 13 '17 at 14:57













  • have try to in reindexing?

    – Ajay Patel
    Jul 26 '18 at 10:10



















  • First make sure that the Elasticsearch supports Magento EE version 2.1.x. From their documentation, If you get the Elasticsearch software from the Elasticsearch Linux repository, we support versions 2.x. If you get the Elasticsearch software from their Elasticsearch-PHP repository, we support the 2.0 branch.

    – Elavarasan
    Jun 13 '17 at 7:27













  • @Elavarasan - I have followed the docs provided by Magento on the Devdocs. Unless they haven't updated the doc for the newer Magneto version or if something is missing on my end it should be working fine as per the configurations we have in the Devdocs.

    – VK Ranjith
    Jun 13 '17 at 14:57













  • have try to in reindexing?

    – Ajay Patel
    Jul 26 '18 at 10:10

















First make sure that the Elasticsearch supports Magento EE version 2.1.x. From their documentation, If you get the Elasticsearch software from the Elasticsearch Linux repository, we support versions 2.x. If you get the Elasticsearch software from their Elasticsearch-PHP repository, we support the 2.0 branch.

– Elavarasan
Jun 13 '17 at 7:27







First make sure that the Elasticsearch supports Magento EE version 2.1.x. From their documentation, If you get the Elasticsearch software from the Elasticsearch Linux repository, we support versions 2.x. If you get the Elasticsearch software from their Elasticsearch-PHP repository, we support the 2.0 branch.

– Elavarasan
Jun 13 '17 at 7:27















@Elavarasan - I have followed the docs provided by Magento on the Devdocs. Unless they haven't updated the doc for the newer Magneto version or if something is missing on my end it should be working fine as per the configurations we have in the Devdocs.

– VK Ranjith
Jun 13 '17 at 14:57







@Elavarasan - I have followed the docs provided by Magento on the Devdocs. Unless they haven't updated the doc for the newer Magneto version or if something is missing on my end it should be working fine as per the configurations we have in the Devdocs.

– VK Ranjith
Jun 13 '17 at 14:57















have try to in reindexing?

– Ajay Patel
Jul 26 '18 at 10:10





have try to in reindexing?

– Ajay Patel
Jul 26 '18 at 10:10










1 Answer
1






active

oldest

votes


















0














@Rajith: "magento2_product_1" is the alias of "magento2_product_1_v1" the index that is created on ES is correct. Magento should be able to find the
correct index through the alias "magento2_product_1".



It is working without any issues on Magento Devbox which uses Elastic Search 2.4.5 and I am running Magento EE 2.1.6.



There should be something wrong in your Elastic Search configuration or the permissions.






share|improve this answer
























  • The issue is with alias. When I checked the index value for "magento2_product_1_v1" I couldn't find any alias assigned to it.

    – VK Ranjith
    Jun 19 '17 at 15:29











  • @Nirmal : Can you help me setting up elastic search on my magento instance ? here is the link to the question: magento.stackexchange.com/questions/184306/…

    – Sejal Shah
    Jul 19 '17 at 5:21











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f178295%2fmagento-2-elasticsearch-root-mapping-definition-has-unsupported%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














@Rajith: "magento2_product_1" is the alias of "magento2_product_1_v1" the index that is created on ES is correct. Magento should be able to find the
correct index through the alias "magento2_product_1".



It is working without any issues on Magento Devbox which uses Elastic Search 2.4.5 and I am running Magento EE 2.1.6.



There should be something wrong in your Elastic Search configuration or the permissions.






share|improve this answer
























  • The issue is with alias. When I checked the index value for "magento2_product_1_v1" I couldn't find any alias assigned to it.

    – VK Ranjith
    Jun 19 '17 at 15:29











  • @Nirmal : Can you help me setting up elastic search on my magento instance ? here is the link to the question: magento.stackexchange.com/questions/184306/…

    – Sejal Shah
    Jul 19 '17 at 5:21
















0














@Rajith: "magento2_product_1" is the alias of "magento2_product_1_v1" the index that is created on ES is correct. Magento should be able to find the
correct index through the alias "magento2_product_1".



It is working without any issues on Magento Devbox which uses Elastic Search 2.4.5 and I am running Magento EE 2.1.6.



There should be something wrong in your Elastic Search configuration or the permissions.






share|improve this answer
























  • The issue is with alias. When I checked the index value for "magento2_product_1_v1" I couldn't find any alias assigned to it.

    – VK Ranjith
    Jun 19 '17 at 15:29











  • @Nirmal : Can you help me setting up elastic search on my magento instance ? here is the link to the question: magento.stackexchange.com/questions/184306/…

    – Sejal Shah
    Jul 19 '17 at 5:21














0












0








0







@Rajith: "magento2_product_1" is the alias of "magento2_product_1_v1" the index that is created on ES is correct. Magento should be able to find the
correct index through the alias "magento2_product_1".



It is working without any issues on Magento Devbox which uses Elastic Search 2.4.5 and I am running Magento EE 2.1.6.



There should be something wrong in your Elastic Search configuration or the permissions.






share|improve this answer













@Rajith: "magento2_product_1" is the alias of "magento2_product_1_v1" the index that is created on ES is correct. Magento should be able to find the
correct index through the alias "magento2_product_1".



It is working without any issues on Magento Devbox which uses Elastic Search 2.4.5 and I am running Magento EE 2.1.6.



There should be something wrong in your Elastic Search configuration or the permissions.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jun 18 '17 at 15:49









Nirmal AryaNirmal Arya

1




1













  • The issue is with alias. When I checked the index value for "magento2_product_1_v1" I couldn't find any alias assigned to it.

    – VK Ranjith
    Jun 19 '17 at 15:29











  • @Nirmal : Can you help me setting up elastic search on my magento instance ? here is the link to the question: magento.stackexchange.com/questions/184306/…

    – Sejal Shah
    Jul 19 '17 at 5:21



















  • The issue is with alias. When I checked the index value for "magento2_product_1_v1" I couldn't find any alias assigned to it.

    – VK Ranjith
    Jun 19 '17 at 15:29











  • @Nirmal : Can you help me setting up elastic search on my magento instance ? here is the link to the question: magento.stackexchange.com/questions/184306/…

    – Sejal Shah
    Jul 19 '17 at 5:21

















The issue is with alias. When I checked the index value for "magento2_product_1_v1" I couldn't find any alias assigned to it.

– VK Ranjith
Jun 19 '17 at 15:29





The issue is with alias. When I checked the index value for "magento2_product_1_v1" I couldn't find any alias assigned to it.

– VK Ranjith
Jun 19 '17 at 15:29













@Nirmal : Can you help me setting up elastic search on my magento instance ? here is the link to the question: magento.stackexchange.com/questions/184306/…

– Sejal Shah
Jul 19 '17 at 5:21





@Nirmal : Can you help me setting up elastic search on my magento instance ? here is the link to the question: magento.stackexchange.com/questions/184306/…

– Sejal Shah
Jul 19 '17 at 5:21


















draft saved

draft discarded




















































Thanks for contributing an answer to Magento Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f178295%2fmagento-2-elasticsearch-root-mapping-definition-has-unsupported%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Polycentropodidae

Magento 2 Error message: Invalid state change requested

Paulmy