现在我们开始一些简单的搜索。
运行检索的一共有两种方式:
一种是通过发送搜索参数REST请求URL,另一种是发送请求主体
1.发送搜索参数REST请求
GET /bank/_search?q=*&sort=account_number:asc&pretty
返回结果
{
"took" : 63,
"timed_out" : false,
"_shards" : {
"total" : 5,
"successful" : 5,
"failed" : 0
},
"hits" : {
"total" : 1000,
"max_score" : null,
"hits" : [ {
"_index" : "bank",
"_type" : "account",
"_id" : "0",
"sort": [0],
"_score" : null,
"_source" : {"account_number":0,"balance":16623,"firstname":"Bradshaw","lastname":"Mckenzie","age":29,"gender":"F","address":"244 Columbus Place","employer":"Euron","email":"bradshawmckenzie@euron.com","city":"Hobucken","state":"CO"}
}, {
"_index" : "bank",
"_type" : "account",
"_id" : "1",
"sort": [1],
"_score" : null,
"_source" : {"account_number":1,"balance":39225,"firstname":"Amber","lastname":"Duke","age":32,"gender":"M","address":"880 Holmes Lane","employer":"Pyrami","email":"amberduke@pyrami.com","city":"Brogan","state":"IL"}
}, ...
]
}
}
返回结果我们分析下
took - 弹性搜索执行搜索的时间(以毫秒为单位)
timed_out - 告诉我们搜索是否超时
_shards - 告诉我们搜索了多少个分片,以及对成功/失败的搜索分片的计数
hits - 搜索结果
hits.total - 符合我们搜索条件的文件总数
hits.hits - 实际搜索结果数组(默认为前10个文档)
hits.sort - 结果的排序键(如果按分数排序,则丢失)
hits._score和max_score-忽略这些字段现在
2.发送请求主体
GET /bank/_search
{
"query": { "match_all": {} },
"sort": [
{ "account_number": "asc" }
]
}
两者的区别在于
这里的区别在于,我们不会传递q=*URI,而是向_searchAPI 发送一个JSON样式的查询请求体。我们将在下一节讨论这个JSON查询。
重要的是要明白,一旦您获得了搜索结果,Elasticsearch就完成了该请求,并且不会保留任何类型的服务器端资源或打开游标到您的结果中。这与许多其他平台(如SQL)形成鲜明对比,您可能最初会先查询查询结果的部分子集,然后如果要获取(或浏览)其余部分,则必须不断返回到服务器的结果使用某种有状态的服务器端游标。