You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Michael Russo (Jira)" <ji...@apache.org> on 2021/05/06 16:47:00 UTC

[jira] [Comment Edited] (LEGAL-571) [Usergrid] Verify changes in Elasticsearch Licensing

    [ https://issues.apache.org/jira/browse/LEGAL-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17340309#comment-17340309 ] 

Michael Russo edited comment on LEGAL-571 at 5/6/21, 4:46 PM:
--------------------------------------------------------------

Thanks for the quick response.

Yeah it looks like the last safe version to use is 7.1. However, the Usergrid codebase only relies on the client libraries for Elasticsearch as Usergrid is an application on top of Elasticsearch. Anyone who chooses to deploy Usergrid, would need to install/run Elasticsearch themself. The Elasticsearch FAQ mentions:

"If you build applications on top of Elasticsearch, nothing changes for you. Our client libraries continue to be licensed under Apache 2.0. If you use plugins on top of Elasticsearch or Kibana, nothing changes for you."

It appears that even their latest client version uses the Apache 2.0 license: [https://www.elastic.co/guide/en/elasticsearch/client/java-rest/7.12/_license_2.html]

If I understand it correctly, does this mean we just need to ensure that if/when Usergrid is updated to support later versions of Elasticsearch, we must ensure that we're using the correct client which is Apache 2.0 licensed?

On a side note, the Usergrid CI build/test process does install Elasticsearch in order to run the tests. I'm not sure how that's affected by the license changes. Although, maybe it's not a concern for now since Usergrid still only supports up to Elasticsearch 1.7.x and there are no immediate plans to change that. 


was (Author: mrusso):
Yeah it looks like the last safe version to use is 7.1. However, the Usergrid codebase only relies on the client libraries for Elasticsearch as Usergrid is an application on top of Elasticsearch. Anyone who chooses to deploy Usergrid, would need to install/run Elasticsearch themself. The Elasticsearch FAQ mentions:

"If you build applications on top of Elasticsearch, nothing changes for you. Our client libraries continue to be licensed under Apache 2.0. If you use plugins on top of Elasticsearch or Kibana, nothing changes for you."

It appears that even their latest client version uses the Apache 2.0 license: https://www.elastic.co/guide/en/elasticsearch/client/java-rest/7.12/_license_2.html

If I understand it correctly, does this mean we just need to ensure that if/when Usergrid is updated to support later versions of Elasticsearch, we must ensure that we're using the correct client which is Apache 2.0 licensed?


On a side note, the Usergrid CI build/test process does install Elasticsearch in order to run the tests. I'm not sure how that's affected by the license changes. Although, maybe it's not a concern for now since Usergrid still only supports up to Elasticsearch 1.7.x and there are no immediate plans to change that. 

> [Usergrid] Verify changes in Elasticsearch Licensing
> ----------------------------------------------------
>
>                 Key: LEGAL-571
>                 URL: https://issues.apache.org/jira/browse/LEGAL-571
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Michael Russo
>            Priority: Major
>
> Usergrid (usergrid.apache.org/[https://github.com/apache/usergrid)] leverages the Elasticsearch client library for interacting with the Elasticearch. Elasticsearch is a pre-requisite for running Usergrid (much like an app server requiring the use of a database). Usergrid does not embed the Elasticsearch server into its application.
> Elasticsearch has been making some licensing changes recently: [https://www.elastic.co/pricing/faq/licensing#summarize-changes]
> The licensing changes do not seem to affect the client libraries, but I wanted to consult and verify this. Usergrid source code is currently using the older Elasticsearch v1.7.5 libraries which appear to be unaffected by the licensing changes(1.7 Branch - https://github.com/elastic/elasticsearch/blob/1.7/LICENSE.txt).
> Can someone help confirm that Usergrid's usage of Elasticsearch falls in-line with the correct use of the new Elasticsearch licensing? I realize that if Usergrid upgrades to newer versions of Elasticsearch or uses Elasticsearch in a different way, the license should be re-evaluated. Any other concerns or thoughts?
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org