1、前情提要：
https://www.elastic.co/guide/en/elasticsearch/client/java-api-client/current/installation.html
以上是Elasticsearch对接Java的官方文档（pom依赖部分）
我本地Windows安装的Elasticsearch也是8.15.3版本
2、启动报错
***************************
APPLICATION FAILED TO START
***************************Description:An attempt was made to call a method that does not exist. The attempt was made from the following location:co.elastic.clients.transport.rest_client.SafeResponseConsumer.<clinit>(SafeResponseConsumer.java:52)The following method did not exist:org.elasticsearch.client.RequestOptions$Builder.setHttpAsyncResponseConsumerFactory(Lorg/elasticsearch/client/HttpAsyncResponseConsumerFactory;)Lorg/elasticsearch/client/RequestOptions$Builder;The method's class, org.elasticsearch.client.RequestOptions$Builder, is available from the following locations:jar:file:/C:/repository/java/org/elasticsearch/client/elasticsearch-rest-client/6.4.3/elasticsearch-rest-client-6.4.3.jar!/org/elasticsearch/client/RequestOptions$Builder.classIt was loaded from the following location:file:/C:/repository/java/org/elasticsearch/client/elasticsearch-rest-client/6.4.3/elasticsearch-rest-client-6.4.3.jarAction:Correct the classpath of your application so that it contains a single, compatible version of org.elasticsearch.client.RequestOptions$Builder报错翻译：大意是指正在调用一个不存在的method，这个method对应的class在我的本地maven仓库的xxx路径，并提到了elasticsearch-rest-client的版本，给出的建议是纠正该client的唯一性&兼容性……
我Google了一下报错内容，在Elasticsearch官网中找到了一个类似的issue，官方给出的回答是elasticsearch-rest-client版本不对，但是那个issue最后并未被发起者确认解决问题，而是在一段时间后自动关闭了。
3、依赖分析
发现官方推荐的依赖中集成的elasticsearch-rest-client版本是6.4.3而非8.15.3
因此尝试手动添加elasticsearch-rest-client8.15.3版本的依赖
<dependency><groupId>org.elasticsearch.client</groupId><artifactId>elasticsearch-rest-client</artifactId><version>8.15.3</version></dependency>再次启动项目，启动成功。
起初我以为是阿里镜像中上传的elasticsearch-java依赖有误，在调试过程中，我尝试把maven的settings.xml文件中的阿里镜像替换成Apache仓库，发现仍然存在该问题，因此可以确定应该是官方制作依赖时留下的bug？
