CRUD(Create, Retrieve, Update, Delete)是数据库系统的四种基本操做,分别表示建立、查询、更改、删除,俗称“增删改查”。Elasticsearch做为NoSQL数据库(虽然ES是为搜索引擎而生的,但我更愿意将其看做带有强大文本搜索功能的NoSQL)。html
如下示例基于Elasticsearch 2.4版本。java
在默认状况下,ES的REST接口的端口号为9200,对接Java client的端口号为9300。shell
Create操做为向index中索引文档,若index不存在则ES会自动建立;数据库
$ curl -XPUT 'http://localhost:9200/twitter/tweet/1' -d '{<json data>}'
Java API("org.elasticsearch" % "elasticsearch" % "2.4.1")经过TransportClient
与ES集群链接,CRUD操做即是基于此而实现的。json
final Settings settings = Settings.settingsBuilder() .put("client.transport.sniff", true) .put("client.transport.ping_timeout", 20, TimeUnit.SECONDS) .put("client", true) .put("data", false) .put("cluster.name", "<cluster name>") .build(); Client client = TransportClient.builder() .settings(settings).build() .addTransportAddresses( new InetSocketTransportAddress(InetAddress.getByName("host1"), 9300), new InetSocketTransportAddress(InetAddress.getByName("host2"), 9300));
Index Java API建立index或索引document:api
import org.elasticsearch.action.index.IndexResponse; IndexResponse response = client.prepareIndex("twitter", "tweet") .setSource(documentJson) .get();
ES的查询DSL大体能够分为两种:curl
count(*)
,表示的是doc命中数,能够嵌套子aggs;avg
、max
、sum
等聚合函数,可是不能嵌套子aggs;ES的Query DSL功能实在是强大,在本文短短的篇幅中很难阐述彻底,故只列举了两个简单实例。在之前的项目中,我使用过1.7
版本ES,后来发现2.0.0-beta1
版本及以后DSL语法发生很大的变化,好比filtered
、and
、or
等被废弃掉了,而被bool
取而代之;对应的Java API支持链式操做,与Java 8配合写起来很是舒服。elasticsearch
REST经过_search
接口进行DSL查询:ide
$ curl -XGET 'localhost:9200/<index>/_search?pretty' -d'{<dsl>}'
实战:List<List<String>> idsList
做为过滤条件,其中内一层为and关系、内二层为or关系;而后多字段(为bucketSizeMap
的key)aggs,Java 8实现:函数
BoolQueryBuilder mustQueryBuilder = boolQuery(); if (!(idsList.size() == 1 && idsList.get(0).isEmpty())) { mustQueryBuilder = idsList.stream().reduce( boolQuery(), (mustQB, ids) -> { BoolQueryBuilder shouldQB = ids.stream().reduce(boolQuery(), (qb, id) -> qb.should(termQuery(SearchSystem.getEsType(id, idMap), id)), BoolQueryBuilder::should); return mustQB.must(shouldQB); }, BoolQueryBuilder::must); } SearchRequestBuilder searchRequestBuilder = client.prepareSearch(indexName) .setSearchType(SearchType.DFS_QUERY_THEN_FETCH) .setQuery(mustQueryBuilder); for (Map.Entry<String, Integer> entry : bucketSizeMap.entrySet()) { AggregationBuilder aggregationBuilder = AggregationBuilders .terms(entry.getKey()) .field(entry.getKey()).size(entry.getValue()); searchRequestBuilder.addAggregation(aggregationBuilder); } SearchResponse response = searchRequestBuilder.execute().actionGet();
Bucket Aggregations支持filter aggs,即知足过滤条件后作aggs,
aggs: <aggs_name>: filter: aggs:
其与filter query + aggs在功能上是等价的,
query: bool: filter: aggs:
可是,经测试发现filter query + aggs是比filter aggs查询要快。
update为document级别的操做,即仅支持对某个具体document进行更新;REST经过_update
接口:
$ curl -XPOST 'localhost:9200/<_index>/<_type>/<_id>/_update' -d '{<data>}'
Java API则有两种实现方式:UpdateRequest
+ update
与prepareUpdate
,
// case 1 UpdateRequest updateRequest = new UpdateRequest(); updateRequest.index("index"); updateRequest.type("type"); updateRequest.id("1"); updateRequest.doc(jsonBuilder() .startObject() .field("gender", "male") .endObject()); client.update(updateRequest).get(); // case 2 client.prepareUpdate("ttl", "doc", "1") .setDoc(jsonBuilder() .startObject() .field("gender", "male") .endObject()) .get();
delete操做一般都伴随着检查index是否存在(exist),exist的RESTful接口与Java API分别以下:
$ curl -XHEAD -i 'http://localhost:9200/twitter'
client.admin().indices() .prepareExists(indexName) .execute().actionGet().isExists();
ES提供了三种粗细粒度的删除操做:
RESTful接口:
-- delete complete index $ curl -XDELETE 'http://localhost:9200/<indexname>' -- delete a type in index $ curl -XDELETE 'http://localhost:9200/<indexname>/<typename>' -- delete a particular document $ curl -XDELETE 'http://localhost:9200/<indexname>/<typename>/<documentId>
Java API实现:
// delete complete index client.admin().indices().delete(new DeleteIndexRequest("<indexname>")).actionGet(); // delete a type in index client.prepareDelete().setIndex("<indexname>").setType("<typename>").setId("*").execute().actionGet(); // delete a particular document client.prepareDelete().setIndex("<indexname>").setType("<typename>").setId("<documentId>").execute().actionGet(); // or DeleteResponse response = client.prepareDelete("twitter", "tweet", "1") .execute() .actionGet();