| Subject: | Can't use Elasticsearch with Elastic::Model on case in-sensitive file systems |
We use both ElasticSearch directly and Elastic::Model which depends on ElasticSearch. We could use the new Elasticsearch::Compat to handle the case-insenstive issue when dealing with migrating ElasticSearch to Elasticsearch directly, but we still have a problem with Elastic::Model.
Given the potential for case-insenstive file systems, the naming choice of 'Elasticsearch' is very problematic to current users of Elastic::Model as there is no upgrade path available until something is done about Elastic::Model and it's dependency on ElasticSearch.