Issue a warning when elasticsearch-py version doesn't match cluster major.minor version
See original GitHub issueElasticsearch change: https://github.com/elastic/elasticsearch/pull/63097
So, with 7.10, now all URLs that point to _ml/inference/*
should move to _ml/trained_models/*
to prevent getting deprecation header warnings.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Migrating to 8.0 | Elasticsearch Python Client [master] | Elastic
You'll likely notice after upgrading the client to 8.0 your code is either raising errors or DeprecationWarning to signal where you need to...
Read more >Python Elasticsearch Client - Read the Docs
Language clients are forward compatible; meaning that clients support communicating with greater minor versions of Elasticsearch.
Read more >elasticsearch-py - Read the Docs
If your application uses async/await in Python you can install with the async extra ... communicating with greater or equal minor versions of...
Read more >elasticsearch - PyPI
Python client for Elasticsearch. ... python -m pip install elasticsearch[async] ... communicating with greater or equal minor versions of Elasticsearch.
Read more >Elasticsearch integration - GitLab Docs
If you are using a compatible version and after connecting to OpenSearch, you get the message Elasticsearch version not compatible , unpause indexing....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So we shouldn’t need to change anything here. I’m considering adding a warning that complains that the given
elasticsearch
library doesn’t match the connected Elasticsearch cluster to avoid problems like this when using experimental features in the future 😃Now that many machine learning features aren’t experimental / beta anymore I think we can close this.