Hello everyone, My customer is currently facing a versioning problem. We have an application 'A' that depends (Maven) of ElasticSearch API, which communicates by TransportClient with centralized ElasticSearch Server 'B'.
The problem is : when we upgrades 'B', we need to upgrade the Maven dependency in application 'A', which is not a desired coupling design in the long term. I guess this is a common problem for many companies that you should be aware of already. I saw some topics that said ES promised to leverage this design by avoiding being version dependant in a future API version. Right now, we are aiming either to : 1) Wait for a solution from ES (in a reasonable time) 2) Migrate completely to a full REST architecture bypassing the API I hope you can address the 1) before thinking about the 2). What can you say about this problem and how could/would you solution it ? Best regards, Amaury FAGES. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b2e13fe4-1da4-4a76-8b03-4c0e553cd887%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
