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

[disclaimer: I work Elastic]

The license change[1][2] announced yesterday will have no impact on Magento users using Elasticsearch.

The change involves the source code of Elasticsearch, which is moving from Apache 2.0 to be dual licensed under the Elastic License and SSPL. However the users of Magento are not typically building Elasticsearch from source directly.

The default distribution is free to use here, has no copyleft aspects, and will remain under the Elastic License as it as been for the last few years. We have thousands of folks using our default distribution with Magento today.
For folks who are using the Apache 2.0 licensed distribution, you will need to switch to the default distribution when you upgrade to 7.11 or above, which includes many additional free features, like encrypted networking and role-based access control, etc.

We have an FAQ at [2] that should help clarify most questions, and we're happy to answer additional questions at elastic_license@elastic.co. This change should not impact users of Magento.

[1] https://www.elastic.co/blog/licensing-change
[2] https://www.elastic.co/pricing/faq/licensing

It does affect most enterprise users as their legal departments typically disallow using software under non-opensource licenses (such as SSPL in OSI sense). At least it invokes lengthy legal approval/exception processes. I'm not a legal expert but I heared that SSPL induces a lot of legal risks because the wording is vague in a lot of points. I know a few companies which even stricly disallow using Elasicsearch 7.11+.

Hello @YiffyToys @jabdoa2 @skearns64

Magento team aware of it and work in progress now.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

I think this still has some relevance @ Stale Bot

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.

Hi @engcom-Delta. 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.

It looks like Adobe is planning to move to OpenSearch according to the roadmap they released yesterday.

Hi @YiffyToys

Thanks for your contribution and collaboration.
As per the @hostep comment magento is now supporting OpenSearch in there compatible version. Please refer the document for your reference.
Kindly close the issue.

magento is now supporting OpenSearch in there compatible version.

Sadly there is no OpenSearch for Debian for the immediate future.
So an upgrade is not possible yet.
Hopefully they will keep supporting the current Elastic version until stable packages of OpenSearch exist.
opensearch-project/opensearch-build#28

Hi @engcom-Lima. 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.

Hi @YiffyToys ,

As per above comment there will be no impact on Magento users .
Hence, marking this issue as non-issue. If you are facing any issue kindly create new ticket.

Thanks

I’m using EUI or Elastic Charts in my application outside of Kibana, how does this affect me?
If your application is not a hosted or managed service, you may not be affected at all. If you would like clarification or have additional questions, please reach out to us at elastic_license@elastic.co.

what does this mean?

can I use EUI for the UI of one of the property management applications which does not use any Kibana or ES, and host it and sell this to client? I am not legal expert , please guide me