Elasticsearch DocWriteResponse type字段为空致解析失败求助

问题描述 #

解析Elasticsearch的Bulk响应时触发java.util.Objects.requireNonNull空指针异常，原因是DocWriteResponse中被标记为弃用的type字段为空，但该字段在7.X版本的客户端API中仍为必填项，导致解析失败。已知升级到8.0.0 API可解决，但服务器端为7.X版本，需保持兼容性，求可行方案。

错误栈信息 #

java.io.IOException: Unable to parse response body for Response{requestLine=POST /_bulk?timeout=1m HTTP/1.1, host=xxx, response=HTTP/1.1 200 OK} 
at org.elasticsearch.client.RestHighLevelClient$1.onSuccess(RestHighLevelClient.java:1665) [elasticsearch-rest-high-level-client-7.6.1.jar:7.6.1] 
at org.elasticsearch.client.RestClient$FailureTrackingResponseListener.onSuccess(RestClient.java:590) [elasticsearch-rest-client-7.6.1.jar:7.6.1] 
at org.elasticsearch.client.RestClient$1.completed(RestClient.java:333) [elasticsearch-rest-client-7.6.1.jar:7.6.1] 
at org.elasticsearch.client.RestClient$1.completed(RestClient.java:327) [elasticsearch-rest-client-7.6.1.jar:7.6.1] 
at org.apache.http.concurrent.BasicFuture.completed(BasicFuture.java:122) [httpcore-4.4.14.jar!/:4.4.14] 
at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:181) [httpasyncclient-4.1.4.jar!/:4.1.4] 
at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:448) [httpcore-nio-4.4.14.jar!/:4.4.14] 
at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.inputReady(HttpAsyncRequestExecutor.java:338) [httpcore-nio-4.4.14.jar!/:4.4.14] 
at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:265) [httpcore-nio-4.4.14.jar!/:4.4.14] 
at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81) [httpasyncclient-4.1.4.jar!/:4.1.4] 
at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39) [httpasyncclient-4.1.4.jar!/:4.1.4] 
at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:121) [httpcore-nio-4.4.14.jar!/:4.4.14] 
at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162) [httpcore-nio-4.4.14.jar!/:4.4.14] 
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337) [httpcore-nio-4.4.14.jar!/:4.4.14] 
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315) [httpcore-nio-4.4.14.jar!/:4.4.14] 
at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276) [httpcore-nio-4.4.14.jar!/:4.4.14] 
at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104) [httpcore-nio-4.4.14.jar!/:4.4.14] 
at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:591) [httpcore-nio-4.4.14.jar!/:4.4.14] 
at java.lang.Thread.run(Thread.java:833) [?:?] Caused by: java.lang.NullPointerException at java.util.Objects.requireNonNull(Objects.java:208) ~[?:?] 
at org.elasticsearch.action.DocWriteResponse.<init>(DocWriteResponse.java:127) ~[elasticsearch-7.6.1.jar:7.6.1] 
at org.elasticsearch.action.index.IndexResponse.<init>(IndexResponse.java:50) ~[elasticsearch-7.6.1.jar:7.6.1] 
at org.elasticsearch.action.index.IndexResponse.<init>(IndexResponse.java:39) ~[elasticsearch-7.6.1.jar:7.6.1] 
at org.elasticsearch.action.index.IndexResponse$Builder.build(IndexResponse.java:103) ~[elasticsearch-7.6.1.jar:7.6.1] 
at org.elasticsearch.action.index.IndexResponse$Builder.build(IndexResponse.java:100) ~[elasticsearch-7.6.1.jar:7.6.1] 
at org.elasticsearch.action.bulk.BulkItemResponse.fromXContent(BulkItemResponse.java:158) ~[elasticsearch-7.6.1.jar:7.6.1] 
at org.elasticsearch.action.bulk.BulkResponse.fromXContent(BulkResponse.java:196) ~[elasticsearch-7.6.1.jar:7.6.1] 
at org.elasticsearch.client.RestHighLevelClient.parseEntity(RestHighLevelClient.java:1793) ~[elasticsearch-rest-high-level-client-7.6.1.jar:7.6.1] 
at org.elasticsearch.client.RestHighLevelClient.lambda$performRequestAsyncAndParseEntity$10(RestHighLevelClient.java:1581) ~[elasticsearch-rest-high-level-client-7.6.1.jar:7.6.1] 
at org.elasticsearch.client.RestHighLevelClient$1.onSuccess(RestHighLevelClient.java:1663) [elasticsearch-rest-high-level-client-7.6.1.jar:7.6.1] ... 18 more

可行解决方案 #

方案1：显式指定文档type #

在构造Bulk请求的每个操作时，显式指定type字段为_doc（Elasticsearch 7.X的默认type值）。例如：

IndexRequest indexRequest = new IndexRequest("your_index_name");
indexRequest.type("_doc"); // 显式指定type
indexRequest.id("doc_id");
indexRequest.source("field", "value");

这样服务器返回的响应中会包含type字段，避免客户端解析时触发非空校验。

方案2：升级客户端到7.X最新稳定版 #

Elasticsearch 7.X后续的小版本（如7.17系列）修复了弃用字段必填的兼容问题，将客户端升级到与服务器同大版本的最新稳定版，既能保持和7.X服务器的兼容性，又能解决解析时的空指针异常。

方案3：自定义响应解析逻辑 #

绕过RestHighLevelClient默认的解析流程，手动处理响应内容：

1. 使用底层的RestClient发送Bulk请求，获取原始JSON响应
2. 自行解析JSON数据，当发现type字段缺失时，默认填充_doc
3. 手动构建BulkResponse对象，跳过默认解析中的非空校验步骤

内容的提问来源于stack exchange，提问作者wsxx