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

issue while executing "php -f vsf_tools.php -- --action full_reindex --store STORE_ID" #53

Closed
webdev-ravi opened this issue Feb 12, 2020 · 4 comments

Comments

@webdev-ravi
Copy link

Hello All,

There seems to be a bug on module configuration and execution, i had a sneek peak and saw that you had an patch on magento2-vsbridge-indexer, please do also look for the same on this repo, beneath is the issue i am faing using your develop branch

PHP Fatal error: Uncaught Elasticsearch\Common\Exceptions\BadRequest400Exception: {"error":{"root_cause":[{"type":"parse_exception","reason":"unknown key [index.mapping.total_fields.limit] for create index"}],"type":"parse_exception","reason":"unknown key [index.mapping.total_fields.limit] for create index"},"status":400} in /var/www/html/magento/lib/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php:610
Stack trace:
#0 /var/www/html/magento/lib/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php(273): Elasticsearch\Connections\Connection->process4xxError(Array, Array, Array)
#1 /var/www/html/magento/lib/vendor/react/promise/src/FulfilledPromise.php(25): Elasticsearch\Connections\Connection->Elasticsearch\Connections{closure}(Array)
#2 /var/www/html/magento/lib/vendor/guzzlehttp/ringphp/src/Future/CompletedFutureValue.php(55): React\Promise\FulfilledPromise->then(Object(Closure), NULL, NULL)
#3 /var/www/html/magento/lib/vendor/guzzlehttp/ringph in /var/www/html/magento/lib/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php on line 610

@afirlejczyk
Copy link
Contributor

afirlejczyk commented Feb 13, 2020

I am not sure of any patch for magento2-vsbridge-indexer..
which ES do you use? Exporting for ES5 worked just fine.

@webdev-ravi
Copy link
Author

I have installed ES7 and using that with this module

@webdev-ravi
Copy link
Author

I am not sure of any patch for magento2-vsbridge-indexer..
which ES do you use? Exporting for ES5 worked just fine.

I have installed ES7 and using that with this module

@afirlejczyk
Copy link
Contributor

afirlejczyk commented Feb 14, 2020

Module does not support ES6+, only ES5.
There is issue for adding support for ES6+ #44

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

No branches or pull requests

2 participants