Elasticsearch6 generation does not exist

[wclshashank]

Preconditions (*)

1. Getting issue while upgrade magento 2.3 to Magento 2.3.1
2. Using Php 7.1.27 version on ubuntu OS

Steps to reproduce (*)

1. After upgrade magento version getting issue on di:compile like

Source class "\Magento\Elasticsearch6\Model\Adapter\FieldMapper\ProductField" for "Magento\Elasticsearch6\Model\Adapter\FieldMapper\ProductFieldMapper" generation does not exist.

2. I have checked class manually, it doesn't exist.

Expected result (*)

1. Issue doesn't appear di compile need to work properly.

Actual result (*)

1. 
2. Please help us to resolve this issue.

[magento-engcom-team]

Hi @wclshashank. 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.

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

• yes
• no

[magento-engcom-team]

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).

  Details

  If 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]

Hi @wclshashank the 2.3.1 release will be 26 how can you upgrade ?

[wclshashank]

HI @engcom-backlog-nazar ,

Ok got it, I didn't check the release date and try to upgrade magneto2 version.

Thanks.

[ghost]

@wclshashank i'm closing this as magento 2.3.0 do not have Elasticsearch 6 module only develop branch. and on 2.3-develop have no this issue.

[juharintanen]

Updated to 2.3.1 now and same error still appears.
Only way around it was to disable Magento_Elasticsearch6 module

That file indeed did not exist

[ghost]

hi @juharintanen i'm will recheck.

[wclshashank]

Hi,

I have this issue due to Amasty module. Amasty module using elasticsearch, which is making issue in compiling.
So i have disable module bin/magento module:disable Amasty_Shopby Amasty_ShopbyPage Amasty_ShopbyBrand
and starts working.

Need to update Amasty module.

Thanks

[juharintanen]

Hi,

I have this issue due to Amasty module. Amasty module using elasticsearch, which is making issue in compiling.
So i have disable module bin/magento module:disable Amasty_Shopby Amasty_ShopbyPage Amasty_ShopbyBrand
and starts working.

Need to update Amasty module.

Thanks

Yep confirmed!
It wasn't that but another Amasty module. Error msg just didn't hint that way at all but good to know.

[ghost]

@wclshashank found internal ticket where this was fixed, wait a little bit i'm share with pr.

[fabio-fafle]

Hi,
from my understanding if you have a plugin on Magento\Elasticsearch\Elasticsearch5\Model\Adapter\FieldMapper\ProductFieldMapper the virtual type Magento\Elasticsearch6\Model\Adapter\FieldMapper\ProductFieldMapper will inherit it and this cause the issue on method
Magento\Setup\Module\Di\Code\Generator\InterceptionConfigurationBuilder::filterNullInheritance
if ($plugins === null || !$this->typeReader->isConcrete($instance)).

It looks like a bug to me.

[csdougliss]

I have the same issue on 2.3.1:

Source class "\Magento\Elasticsearch6\Model\Adapter\FieldMapper\ProductField" for "Magento\Elasticsearch6\Model\Adapter\FieldMapper\ProductFieldMapper" generation does not exist.

Does this require a fix from Magento or from Amasty?

@engcom-backlog-nazar please share the PR

[bahramdavoodi]

Hi @craigcarnell,

I have the same error after run di:compile. if you have Extension Amasty Layered Navigation, you can to try to disable extension Amasty_Shopby and run di:compile.

I hope it helps you.
Thanks

[ghost]

Hi @craigcarnell why reopen ?

[csdougliss]

@engcom-backlog-nazar Because a fix has not been provided by Magento

[csdougliss]

@engcom-backlog-nazar Do you have the PR you mentioned? I need this ASAP please

[ghost]

@craigcarnell no, because this in private repository. https://github.com/magento/magento2ce/pull/3912/files#diff-b2e0d454e4ffd542fa96dc1b7dc225d9

[csdougliss]

@engcom-backlog-nazar Slightly confused, as you offered a fix above. Will create a ticket with Magento "Gold" support..

[hostep]

@engcom-backlog-nazar: can you please link to open sourced repo's please? It would be very interesting to see this fix as other tickets are being created which are probably caused by the same issue.

Just link to commits in this repo if they have already been merged, that would be very much appreciated!

[wclshashank]

Hi @engcom-backlog-nazar ,

Is there any update?

[adamrandazzo]

I can confirm that this seems to be caused by a conflict with the Amasty_ShopBy plugin. I can get it to compile if I disable Amasty_ShopBy OR Magento_Elasticsearch6.

[ghost]

@adamrandazzo so to have this issue we need just add a plugin to ElasticSearch 6 ? can you show where plugin defined ?

[davoc]

Same issue when upgrading from 2.3.0 to 2.3.1 and same solution here - disable Amasty_Shopby and setup:di:compile completes without error

[phoenix128]

I was able to reproduce and it is a general issue related to virtual types with names ending with any autogenerated suffix being pluginized on concrete class.

[Zyles]

Same problem. Not using Amasty_ShopBy ...

[hostep]

Interesting tidbit: if I copy the Elasticsearch6 module into a Magento 2.3.0 installation with the unpatched Amasty module, the same problem occurs. So this is no new bug in 2.3.1.

I also can confirm what @phoenix128 figured out, in that certain names of virtual types can not be used, if they end on for example Mapper or Logger or something like that. Then that last part gets stripped of. This happens over here.
Has this always been the case? Is this expected? Is this documented somewhere?

The WIP fix unfortunately doesn't seem to resolve the problem in my testing.

@maghamed: have you guys already found more info about this problem?

[akosglue]

I got the same error on 2.3.1.
Catalog Search indexer process unknown error: Source class "\Magento\Elasticsearch6\Model\Adapter\FieldMapper\ProductField" for "Magento\Elasticsearch6\Model\Adapter\FieldMapper\ProductFieldMapper" generation does not exist.
After disabling all Amasty extensions the error disappeared.

[bijalbhavsar]

This error occurs after upgrading 2.3.1 and it is bug in Magento 2.3.1. If we see https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/Elasticsearch6/etc/di.xml it is showing below code:

<type name="Magento\Elasticsearch\Elasticsearch5\Model\Adapter\FieldMapper\ProductFieldMapperProxy"> <arguments> <argument name="productFieldMappers" xsi:type="array"> <item name="elasticsearch6" xsi:type="object">Magento\Elasticsearch6\Model\Adapter\FieldMapper\ProductFieldMapper</item> </argument> </arguments> </type>

In above code it states "Magento\Elasticsearch6\Model\Adapter\FieldMapper\ProductFieldMapper" as a argument for productFieldMappers and no such model class file exists.

Review below file path to verify it: https://github.com/magento/magento2/tree/2.3-develop/app/code/Magento/Elasticsearch6/Model/Adapter/FieldMapper

To fix this issue, either we have to remove this code snippet or create a class file for the same.

As per me, It is Magento issue and not relevant to Amasty.

[hostep]

@bijalbhavsar : Magento\Elasticsearch6\Model\Adapter\FieldMapper\ProductFieldMapper exists as a virtual type, see: https://github.com/magento/magento2/blob/2.3.1/app/code/Magento/Elasticsearch6/etc/di.xml#L158

[phoenix128]

My PR (https://github.com/magento/magento2/pull/22046/files) is in WIP status, but I am almost there to fix it. Seems like the issue is divided in two different aspects and now I fixed just one of them. More precisely I just fixed it in the developer mode. Need to fix in production mode.

[phoenix128]

Update:
I just finalized it. Pull request #22046 seems to fix the issue.

[magento-engcom-team]

@sdzhepa Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Component: " label(s) to this ticket based on verification result. If uncertain, you may follow the best guess

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

✅ Confirmed by @sdzhepa
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-99115 were created

Issue Available: @sdzhepa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @wclshashank. Thank you for your report.
The issue has been fixed in #22046 by @phoenix128 in 2.3-develop branch
Related commit(s):

• fa079c94c9c0a6d3cd7d9dca3b52d3394de50934
• 75684cadfe6231e352c959cbd0648612489b533a
• b8ab61b86f05c45343c78c3341920756f888904f
• 6d873304742ee5114ec661d6b799bd2f0a4f3cff

The fix will be available with the upcoming 2.3.2 release.