總結一下elasticsearch java api開發過程當中遇到的一些問題。
elasticsearch版本:5.1.2java
PreBuiltTransportClient找不到
當咱們按elasticsearch老版本2.x同樣引用maven文件時,以下:node
<dependency> <groupId>org.elasticsearch</groupId> <artifactId>elasticsearch</artifactId> <version>5.1.2</version> </dependency>
在咱們建立elasticsearch的TransportClient時候
TransportClient client = new PreBuiltTransportClient(),提示沒法找到PreBuiltTransportClient類。
這是因爲elasticsearch從5.x開始客戶端放在了新的jar包裏,咱們須要引用以下:apache
<dependency> <groupId>org.elasticsearch.client</groupId> <artifactId>transport</artifactId> <version>5.1.2</version> </dependency>
找不到log4j類
執行java查詢時候,報錯以下:api
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/logging/log4j/Logger at org.elasticsearch.common.logging.Loggers.getLogger(Loggers.java:105) at org.elasticsearch.common.logging.Loggers.getLogger(Loggers.java:72) at org.elasticsearch.common.component.AbstractComponent.<init>(AbstractComponent.java:37) at org.elasticsearch.plugins.PluginsService.<init>(PluginsService.java:98) at org.elasticsearch.client.transport.TransportClient.newPluginService(TransportClient.java:94) at org.elasticsearch.client.transport.TransportClient.buildTemplate(TransportClient.java:119) at org.elasticsearch.client.transport.TransportClient.<init>(TransportClient.java:247) at org.elasticsearch.transport.client.PreBuiltTransportClient.<init>(PreBuiltTransportClient.java:125) at org.elasticsearch.transport.client.PreBuiltTransportClient.<init>(PreBuiltTransportClient.java:111) at org.elasticsearch.transport.client.PreBuiltTransportClient.<init>(PreBuiltTransportClient.java:101) Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.Logger at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
只是因爲elasticsearch 5.x中須要log4j的一些依賴,須要添加,在pom.xml中添加以下maven配置:數組
<dependency> <groupId>org.apache.logging.log4j</groupId> <artifactId>log4j-api</artifactId> <version>2.7</version> </dependency> <dependency> <groupId>org.apache.logging.log4j</groupId> <artifactId>log4j-core</artifactId> <version>2.7</version> </dependency>
index級別settings設置錯誤
按照2.x的方式構造Setting,以下:elasticsearch
Settings settings = Settings.builder()
.put("cluster.name", clusterName)
.put("cluster.transport.sniff", true)
.put("index.refresh_interval", "60s")
.build();
在執行客戶端查詢時,報錯以下:maven
java.lang.IllegalArgumentException: node settings must not contain any index level settings
at org.elasticsearch.common.settings.SettingsModule.<init>(SettingsModule.java:131)
at org.elasticsearch.client.transport.TransportClient.buildTemplate(TransportClient.java:133)
at org.elasticsearch.client.transport.TransportClient.<init>(TransportClient.java:247)
at org.elasticsearch.transport.client.PreBuiltTransportClient.<init>(PreBuiltTransportClient.java:125)
at org.elasticsearch.transport.client.PreBuiltTransportClient.<init>(PreBuiltTransportClient.java:111)
at org.elasticsearch.transport.client.PreBuiltTransportClient.<init>(PreBuiltTransportClient.java:101)
即5.x不支持索引級別的設置,即5.x不支持index.refresh_interval配置,且名字也變動了,5.x只支持的Settings配置以下:函數
配置 說明
cluster.name 集羣name
client.transport.sniff 是否支持自動嗅探
client.transport.ignore_cluster_name Set to true to ignore cluster name validation of connected nodes. (since 0.19.4)
client.transport.ping_timeout The time to wait for a ping response from a node. Defaults to 5s.
client.transport.nodes_sampler_interval How often to sample / ping the nodes listed and connected. Defaults to 5s.
所以,咱們配置以下便可:fetch
Settings settings = Settings.builder()
.put("cluster.name", clusterName)
.put("client.transport.sniff", true)
.build();
如何指定返回的字段field
在elasticsearch 2.x版本中,若是咱們想指定查詢返回的字段,可使用fields字段設置,代碼以下:ui
String index = xxx;
String type = xxx;
// 指定要返回的字段
String[] fields = new String[2];
fields[0] = "field1"; // 字段1名稱
fields[1] = "filed2"; // 字段2名稱
// 構造query
SearchRequestBuilder requestBuilder = client.prepareSearch(index);
requestBuilder .setFrom(0).setSize(100)
.setTimeout(TimeValue.timeValueMillis(300))
.setTypes(type)
.addFields(fields);
// bool 條件
BoolQueryBuilder boolQueryBuilder = QueryBuilders.boolQuery();
TermQueryBuilder tqb = QueryBuilders.termQuery("field1", "val1");
boolQueryBuilder.must(tqb);
// set query
requestBuilder.setQuery(boolQueryBuilder);
// get response
SearchResponse response = requestBuilder.execute().actionGet();
// 遍歷返回的字段
SearchHits searchHits = response.getHits();
for (SearchHit hit : searchHits) {
System.out.println(hit.getFields().get("filed1").getValue().toString());
}
可是在5.x中,setFileds函數已經不存在了,那在5.x中經過什麼來指定返回的字段呢,答案是Source字段,經過setFetchSource函數來指定要返回的字段,能夠指定單個filed或者一個filed數組,經過getSource來獲取返回的字段值,其中setFetchSource有三個版本,說明以下:
1. setFetchSource(boolean fetch)
用於指定是否返回字段,默認爲true,若是爲false,則getSource返回null。
2. setFetchSource(String include, String exclude)
用於指定包含的一個字段和排除的一個字段,實際會返回include字段及其對應的值。
3. setFetchSource(String[] includes, String[] excludes)
用於指定包含的多個字段和排除的多個字段。
下面以具體代碼來講明如何獲取:
String index = xxx; String type = xxx; // 指定要返回的字段 String[] fields = new String[2]; fields[0] = "field1"; // 字段1名稱 fields[1] = "filed2"; // 字段2名稱 // 構造query SearchRequestBuilder requestBuilder = client.prepareSearch(index); requestBuilder .setFrom(0).setSize(100) .setTimeout(TimeValue.timeValueMillis(300)) .setTypes(type) // 指定返回的字段,排除字段設爲null .setFetchSource(fields, null); // bool 條件 BoolQueryBuilder boolQueryBuilder = QueryBuilders.boolQuery(); TermQueryBuilder tqb = QueryBuilders.termQuery("field1", "val1"); boolQueryBuilder.must(tqb); // set query requestBuilder.setQuery(boolQueryBuilder); // get response SearchResponse response = requestBuilder.execute().actionGet(); // 遍歷返回的字段 SearchHits searchHits = response.getHits(); for (SearchHit hit : searchHits) { // 注意這裏和2.x不一樣的是使用getSource函數 System.out.println(hit.getSource().get("filed1")); } --------------------- 做者:簡牧 來源:CSDN 原文:https://blog.csdn.net/qq_35799003/article/details/70210919 版權聲明:本文爲博主原創文章,轉載請附上博文連接!