OpenSearch missing i18n stopwords

[vandijkstef]

Preconditions and environment

• Magento 2.4.8-p1
• PHP 8.3
• OpenSearch

Steps to reproduce

Use opensearch on a non en_EN store, preferably a locale defined in module-elasticsearch/etc/stopwords/stopwords_xx_XX.csv.

Expected result

Search excluding terms as defined in module-elasticsearch/etc/stopwords/stopwords_*.xml

Actual result

Search excluding en_EN stopwords ('and') but is including nl_NL stopwords ('en').

en_EN 'A and B' or 'A B' produce the exact same results.
nl_NL 'A en B' or 'A B' should produce the same results, but the first term returns 10x the results.

Additional information

Within module-opensearch, no reference is found to "stopword".

Module-elasticsearch has default stopwords for various different languages available.

Possible relevance to #39809

S2 severity due to too many search results might cause the results page to have 5XX-errors.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @vandijkstef. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

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, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

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

Hello @vandijkstef ,

Thank you for your report and collaboration.

We have attempted to reproduce the issue but were unable to do so. Could you please confirm if we might be missing any details? It would be very helpful if you could provide a more detailed description, including clear steps to reproduce the issue. If possible, please also share a screencast demonstrating the problem.

Thank you!