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

Bulk index operation failed - failed to parse [children_attributes] #201

Closed
johnhughes1984 opened this issue Nov 14, 2016 · 9 comments
Closed
Labels

Comments

@johnhughes1984
Copy link

Hi guys

First off great work on this suite, it's a very impressive open source offering.

We've implemented the suite on one of our sites and we noticing issues with bundle products, which means they keep disappearing from categories (and search) on the frontend of the site.

This is an example of the error output (in system.log) that outputs when the catalogsearch_fulltext index is refreshed:

[2016-11-14 11:00:22] main.ERROR: Bulk index operation failed 12 times in index magento2_default_catalog_product_20161114_110007 for type product Error (mapper_parsing_exception) : failed to parse [children_attributes] Failed doc ids sample : 5802, 5808, 5810, 5814, 5817, 5818, 5824, 5851, 5859, 5867 [] []

The error is in nature similar to the one raised in this ticket: #81

However it refers to 'children attributes', which as all the product Ids listed as samples in the error are bundle products relates to some kind of issue mapping these.

I've also tried turning making all attributes not searchable / used in layered navigation with no success.

It is also worth noting we have around 100 bundle products on the site and only a certain number at any one time have problems (between 10-30 normally) and it does appear to very intermittent.

If you have any ideas / suggestions or have seen this before It'd be appreciated as it has us scratching our heads at the minute!

If you need any more detail please let me know.

Kind regards

@afoucret
Copy link
Contributor

afoucret commented Nov 14, 2016

Hi @johnhughes1984,

Very glad to see you appreciate our work on ElasticSuite. We appreciate a lot such supportive feedback.

For you bug, it would help us a lot if you were able to extract the error from the ElasticSearch logs which should be located into the /var/log/elasticsearchdirectory. Actually they are more accurate than the Magento log which are only aggregating product ids. By the way, it contains the document source indexed ....

@johnhughes1984
Copy link
Author

Sure no problem, will take a look there now

@johnhughes1984
Copy link
Author

Hi @afoucret

Please see log file attached, now I know that exists I'll also have a browse through and see what I can spot.

elasticsuite.log.txt

Many thanks

@afoucret
Copy link
Contributor

Hi @johnhughes1984,

Found !!! The patch should be available very soon (let's say tomorrow). It is only matters of having a array_values somewhere it is currently missing.

I will also need to know what version of ElasticSuite you are currently using in order to target the right branch ....

@afoucret afoucret added the bug label Nov 14, 2016
@johnhughes1984
Copy link
Author

Wow, that was fast! Thanks @afoucret

We're running the latest (I believe), which is 2.2.2

We're also running Magento CE 2.1.2 if it helps at all.

Many thanks for looking at this so quickly, very much appreciated 👍 💯

@afoucret
Copy link
Contributor

Note : Patched proposed in PR #202

afoucret added a commit that referenced this issue Nov 14, 2016
…indexing

Fix #201 : Indexing children attributes of bundle products.
@afoucret
Copy link
Contributor

You can test

@afoucret afoucret reopened this Nov 14, 2016
@afoucret
Copy link
Contributor

You can test it by using the 2.2.x dev branch.
If everything is OK, it will be part of the next release (2.2.3).

Thx for reporting and by advance for your feedback about the patch.

@johnhughes1984
Copy link
Author

Excellent, I can confirm it works great (i.e. no more errors when indexing bundle products).

Many, many thanks!

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

No branches or pull requests

2 participants