Elastic Search issue with Synonyms

[soumiktuban]

Preconditions (*)

1. Magento 2.3.*.
2. Elasticsearch 6+

Also reproducible on 2.4-develop with Elasticsearch7

Steps to reproduce (*)

1. Enable Elasticsearch 6+
2. Add a product with a long name with a slash / in it.
   Example: LSS 3/8"X3/4"X25' EZ-PULL 1/2" INS SWEAT LINESET W/90 END BEND SUCTION LINE INSULATED
3. Add Search Synonyms with a word belongs to the product name.
   Example: center end boot,torpedo boot,horn boot,register boot center end,register boot torpedo
4. Search in the frontend for that exact product.

Expected result (*)

1. Find that particular product without errors.

Actual result (*)

1. Error report: {"0":"Warning: preg_match(): Unknown modifier '8' in /vendor/magento/module-search/Model/SynonymAnalyzer.php on line 96","1":"Can you commit to repository a folder dev/tests/static ? #1 preg_match() called at [vendor/magento/module-search/Model/SynonymAnalyzer.php:96]\n#2 Magento\Search\Model\SynonymAnalyzer->findInArray() called at [vendor/magento/module-search/Model/SynonymAnalyzer.php:71]

Additional info

1. Create a product with below product name as mentioned earlier:
   

2. Create a Search Synonyms (Marketing -> Search Synonyms) and clear the cache as mentioned earlier:
   

3. Copy the entire product name and search in frontend.
   

4. Hit enter
   

5. Here is the message from the report:
   

6. Here is my configuration:
   

[m2-assistant]

Hi @soumiktuban. 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 give me 2.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Oscar. 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.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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. Add label Issue: Confirmed once verification is complete.

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

[engcom-Oscar]

Hello @soumiktuban

Thank you for your report.
Unfortunately, I was not able to reproduce this issue on the latest 2.4-develop code. Probably it was already fixed and will appear in the next release. Or we missed some steps or preconditions.

Could you please recheck it on clean Magento 2.4 installation and confirm?

[soumiktuban]

I don't have a system ready for Magento 2.4 right now. Kindly keep it open till I get a system to confirm.
Please let me know if this issue can be fixed by using a patch on Magento 2.3.*.

Thanks :)

[engcom-Oscar]

Sorry, but we are able to process, collaborate, fix, and deliver pull requests ONLY for Issues that can be reproduced on the latest 2.4-develop public branch.

• Code Contributions: Accepted pull requests and ported code
  Quote

  
  v2.4 Contribution Notice: Magento is focusing development efforts on v2.4, so we are no longer accepting pull requests to the v2.3, v2.2, v2.1, and v2.0 release lines.

[soumiktuban]

Hello @engcom-Oscar

This issue is still reproducible on Magento 2.4
Below snaps are the steps to reproduce the issue:

1. Create a product with below product name as mentioned earlier:
   

2. Create a Search Synonyms (Marketing -> Search Synonyms) and clear the cache as mentioned earlier:
   

3. Copy the entire product name and search in frontend.
   

4. Hit enter
   

5. Here is the message from the report:
   

6. Here is my configuration:
   

Hope this will help you to reproduce the issue.

Thanks,
Soumik

[soumiktuban]

@engcom-Oscar @magento-engcom-team
Any update?
Are you able to reproduce this issue?

[soumiktuban]

@magento-engcom-team @engcom-Oscar - Any update?

[m2-assistant]

Hi @engcom-Bravo. 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.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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. Add label Issue: Confirmed once verification is complete.

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

[denchev]

I can reproduce the issue so @magento I am working on this

[m2-assistant]

Hi @denchev! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[denchev]

@magento add to contributors team

[m2-assistant]

Hi @denchev! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

[denchev]

@magento I am working on this

[magento-engcom-team]

Hi @soumiktuban. Thank you for your report.
The issue has been fixed in #30614 by @denchev in 2.4-develop branch
Related commit(s):

• b21693a04f4d92fc3afb4c530363d9304beb7b2e
• c36f29b1c66720217c52b63b6a79801ff29c5f1e
• b75440eea2c6d2bda4ec588c29cf2876a5d6c9ce
• 64cb4937defb8fdb7dbb8cb98456098b64bb2b8b

The fix will be available with the upcoming 2.4.2 release.