When bringing up TweetSets on the current master branch, indexes will not load. The "Woops! ElasticSearch isn't up. " message displays. Elasticsearch is actually up and running, however.
Because of the way the elasticsearch library is pinned in requirements.txt, in new builds of the server or server-flaskrun containers, the library floats up to 7.14.0 instead of a patch version of 7.10. (This is my fault for misunderstanding how the compatibility operator works.)
The recently released 7.14.0 version of the elasticsearch library introduces a new exception, UnsupportedProductError. That error is being raised: ElasticSearch error: The client noticed that the server is not a supported distribution of Elasticsearch.
I don't understand why our version of Elasticsearch (7.9.2 from an official docker image) is being seen as an unsupported version. There are articles about recent changes in Elasticsearch licensing (example) but according to Elasticsearch's FAQ it would seem our usage is fine.
As a short-term fix, pinning as follows will keep versions from floating up higher than intended:
When bringing up TweetSets on the current master branch, indexes will not load. The "Woops! ElasticSearch isn't up. " message displays. Elasticsearch is actually up and running, however.
Because of the way the
elasticsearchlibrary is pinned inrequirements.txt, in new builds of the server or server-flaskrun containers, the library floats up to 7.14.0 instead of a patch version of 7.10. (This is my fault for misunderstanding how the compatibility operator works.)The recently released 7.14.0 version of the elasticsearch library introduces a new exception, UnsupportedProductError. That error is being raised:
ElasticSearch error: The client noticed that the server is not a supported distribution of Elasticsearch.I don't understand why our version of Elasticsearch (7.9.2 from an official docker image) is being seen as an unsupported version. There are articles about recent changes in Elasticsearch licensing (example) but according to Elasticsearch's FAQ it would seem our usage is fine.
As a short-term fix, pinning as follows will keep versions from floating up higher than intended: