Packaging ElasticSearch (different version for different server API version)

[Adam Cécile <acecile@le-vert.net>]

Hello,


At the moment, python-elasticsearch is only available in version 1.x 
[1], which is pretty useless as it's intended to be used against 
ElasticSearch 1.x servers.

The main problem is that the client is disitributed following multiple 
branches, one for servers running version 1.x, another for version 2.x 
and the last one for 5.x but I really think Debian should provide high 
level Python library for ElasticSearch (next goal is to get the DSL in [3]).

How would you handle that ? For work purpose I created 
python-elasticsearch2 and python3-elasticsearch2 as well as 
python-elasticsearch5 and python3-elasticsearch5.

It's working just fine, and I even think it's a lot saner as I can 
simply do "from elasticsearch5 import ElasticSearch" instead "from 
elasticsearch2 import ElasticSearch" to test my code against a new ES5 
servers cluster.Do you think it's acceptable to "change" upstream 
behavior like this ?

Does it worth an alternative, to provide a default unversionned 
"elasticsearch" module ?


Thanks in advance for your answer,

Best regards, Adam.


[1] https://packages.debian.org/search?keywords=python-elasticsearch

[2] https://elasticsearch-py.readthedocs.io/en/master/#compatibility

[3] https://elasticsearch-dsl.readthedocs.io/