Interesting, I hadn't considered that.

Is there some way to automatically audit packages to ensure they meet WMCS licensing requirements?  It would be unfortunate if I inadvertently grabbed something that wasn't appropriately licensed and started depending on it.

On Jan 11, 2022, at 10:57 AM, Andrew Bogott <abogott@wikimedia.org> wrote:

In addition to fixing your binding issue, opensearch has the added advantage of being permitted on toolforge :)

Elastic search > 7.10 was re-licensed. It's no longer available under an OSI license so running newer elasticsearch versions is not permitted on WMCS.

-Andrew

On 1/10/22 8:49 PM, Roy Smith wrote:
Never mind, I found it.  The problem is that newer versions of elasticsearch (> 7.14?) do over-eager version checking as described here.  I ended up moving to https://opensearch.org/ which looks like it's working.  Apparently this affects multiple language bindings (Python, Ruby, JS, maybe others).

On Jan 10, 2022, at 9:35 PM, Roy Smith <roy@panix.com> wrote:

I'm exploring using elasticsearch in Toolforge.  I'm running Python 3.7, with elasticsearch==7.16.2 installed.  When I run:

def main():
   es = Elasticsearch(['elasticsearch.svc.tools.eqiad1.wikimedia.cloud:80'])
   print(es.info())

I get:

elasticsearch.exceptions.UnsupportedProductError: The client noticed that the server is not a supported distribution of Elasticsearch

Any idea what's wrong?  Are we running some very old version of elasticsearch server?
_______________________________________________
Cloud mailing list -- cloud@lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/



_______________________________________________
Cloud mailing list -- cloud@lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/