You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a pin for elasticsearch<7.14.0 in the common_constraints file but it's not clear if this is a problem specific to course-discovery or a problem with edx-platform as well. Looking at the changelog, the biggest difference with the newer versions of the elastichsearch client is that you have to match the python client version to the corresponding elasticsearch client version or it will fail to startup.
Looking at the PR that added this change, it's not clear what exactly was the error being seen. After speaking with Jeremy at 2U, it looks like 2U is constrained with running elasticsearch 7.10 or opensearch and the newer version of the elasticsearch python library will break with both of those versions which explains the pin.
In the meantime, we'll have to pin numpy<2.0.0 no not block other upgrades because the current pin of elasticsearch depends on a function in numpy that is dropped in numpy 2.0.0.
Once the elasticsearch python package is at version 7.15.0 or greater or it has been removed from the platform, the numpy pin in requirements/constraints.txt can be removed.
The text was updated successfully, but these errors were encountered:
There is a pin for
elasticsearch<7.14.0
in the common_constraints file but it's not clear if this is a problem specific to course-discovery or a problem with edx-platform as well. Looking at the changelog, the biggest difference with the newer versions of the elastichsearch client is that you have to match the python client version to the corresponding elasticsearch client version or it will fail to startup.Looking at the PR that added this change, it's not clear what exactly was the error being seen. After speaking with Jeremy at 2U, it looks like 2U is constrained with running elasticsearch 7.10 or opensearch and the newer version of the elasticsearch python library will break with both of those versions which explains the pin.
In the meantime, we'll have to pin
numpy<2.0.0
no not block other upgrades because the current pin of elasticsearch depends on a function in numpy that is dropped in numpy2.0.0
.Once the elasticsearch python package is at version
7.15.0
or greater or it has been removed from the platform, the numpy pin inrequirements/constraints.txt
can be removed.The text was updated successfully, but these errors were encountered: