I think that there should be specific documentation guidance around this, like “Picking the right Elasticsearch Processors” to avoid issues.
On February 20, 2019 at 08:02:18, Mike Thomsen ([email protected]) wrote: I would like to mark the v5 Elastic bundle as deprecated in 1.10. Per Elastic's official guidelines, the transport API--which it uses--is deprecated in Elastic 7 and to be removed from at least public accessibility in Elastic 8. https://www.elastic.co/guide/en/elasticsearch/client/java-api/master/transport-client.html So I'd like to nudge any users using it to be prepare to align themselves more closely with Elastic's roadmap. ElasticSearch 5.X users can continue to use either the plain vanilla Elastic bundle or start using the new REST API one going forward. The REST APIs don't appear to be changing except in adding new features, so I think we can deprecate and migrate users safely. (Also, it would free up about 30MB-33MB from our binary distro). Thoughts? Mikex
