Originally created by @alex780505 on GitHub (Sep 12, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
Problem Description
Hi,
I have some tools that are used for requesting data on an Elasticsearch v8.1 cluster, that I cannot upgrade.
Until OWUI version 0.6.27, I could use elasticsearch8 as a requirement to add Elasticsearch v8 client.
Since OWUI version 0.6.28, and the move to Elasticsearch9.1 on OWUI, It's not working anymore since v9.1 introduce Elastic-transport v9+ which is uncompatible with v8.
Desired Solution you'd like
A solution could be to uninstall v9.1 and install v8, but it's not a good practice I think.
A better option could be that each tool run in it's own virtualenv so dependencies aren't an issue, whatever the conflicting packet is.
What do you think of this option ?
Alternatives Considered
No response
Additional Context
No response
Originally created by @alex780505 on GitHub (Sep 12, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
Hi,
I have some tools that are used for requesting data on an Elasticsearch v8.1 cluster, that I cannot upgrade.
Until OWUI version 0.6.27, I could use elasticsearch8 as a requirement to add Elasticsearch v8 client.
Since OWUI version 0.6.28, and the move to Elasticsearch9.1 on OWUI, It's not working anymore since v9.1 introduce Elastic-transport v9+ which is uncompatible with v8.
### Desired Solution you'd like
A solution could be to uninstall v9.1 and install v8, but it's not a good practice I think.
A better option could be that each tool run in it's own virtualenv so dependencies aren't an issue, whatever the conflicting packet is.
What do you think of this option ?
### Alternatives Considered
_No response_
### Additional Context
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @alex780505 on GitHub (Sep 12, 2025).
Check Existing Issues
Problem Description
Hi,
I have some tools that are used for requesting data on an Elasticsearch v8.1 cluster, that I cannot upgrade.
Until OWUI version 0.6.27, I could use elasticsearch8 as a requirement to add Elasticsearch v8 client.
Since OWUI version 0.6.28, and the move to Elasticsearch9.1 on OWUI, It's not working anymore since v9.1 introduce Elastic-transport v9+ which is uncompatible with v8.
Desired Solution you'd like
A solution could be to uninstall v9.1 and install v8, but it's not a good practice I think.
A better option could be that each tool run in it's own virtualenv so dependencies aren't an issue, whatever the conflicting packet is.
What do you think of this option ?
Alternatives Considered
No response
Additional Context
No response
@tjbck commented on GitHub (Sep 12, 2025):
If you're using pip install should be addressed with
3e1b14f570in dev