如今让咱们从一些简单的搜索开始。html
搜索参数传递有2种方法:shell
搜索相关的REST API能够从_search
端点访问。下面的例子返回bank
索引中的全部文档:json
API数组
GET /bank/_search?q=*&sort=account_number:asc&pretty
CURLapp
curl -X GET "localhost:9200/bank/_search?q=*&sort=account_number:asc&pretty"
本例采用uri方式传递搜索参数:curl
q=*
搜索索引中的全部文档sort=account_number:asc
搜索结果以字段account_number
升序排列pretty
返回结果以漂亮的JSON格式打印响应:elasticsearch
{ "took" : 55, "timed_out" : false, "_shards" : { "total" : 1, "successful" : 1, "skipped" : 0, "failed" : 0 }, "hits" : { "total" : { "value" : 1000, "relation" : "eq" }, "max_score" : null, "hits" : [ { "_index" : "bank", "_type" : "_doc", "_id" : "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" }, "sort" : [ 0 ] }, { "_index" : "bank", "_type" : "_doc", "_id" : "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" }, "sort" : [ 1 ] }, ... ] } }
看一下响应中的重要字段:ide
took
– 搜索时间(毫秒)timed_out
– 搜索是否超时_shards
– 搜索了多少分片,搜索分片的成功/失败计数hits
– 搜索结果hits.total
– 搜索命中总数信息
hits.total.value
- 命中总数hits.total.relation
- 取值eq(等于)/gte(大于等于),表示hits.total.value
与实际的搜索命中数量的关系。hits.hits
– 实际的搜索结果数组(默认为前10个文档)hits.sort
- 结果排序键(若是按分数排序,则忽略)hits._score
与 max_score
- 分数是衡量文档与搜索条件匹配程度的一个指标。分数越高,文档越相关,分数越低,文档越不相关。并不老是须要生成分数,需不须要Elasticsearch会自动判断,以免计算无用的分数。若是搜索结果不少,超过必定数量后,一般就再也不统计,只是笼统地表示为:搜索结果超过XXXX个。hits.total
的准确性由请求参数track_total_hits
控制,当track_total_hits
为true
时,搜索时将精确地跟踪总命中数(“relationship”:“eq”)。track_total_hits
默认值为10,000,意味着总命中数能够精确地跟踪到10000个文档,若是超过10000,会表示为超过10000个结果,以下所示:ui
"total" : { "value" : 10000, "relation" : "gte" },
经过将track_total_hits
显式地设置为true
,能够强制进行准确计数。详细信息,请参阅request body文档。url
一样的例子,使用请求体(request body)发送搜索参数:
API
GET /bank/_search { "query": { "match_all": {} }, "sort": [ { "account_number": "asc" } ] }
CURL
curl -X GET "localhost:9200/bank/_search" -H 'Content-Type: application/json' -d' { "query": { "match_all": {} }, "sort": [ { "account_number": "asc" } ] } '
能够看到,没有在URI中传递q=*
,而是向_search API
传递json风格的请求体,下一节中会详细讨论。
注意,一旦得到了搜索结果,Elasticsearch就会结束此次搜索,不会再维护任何服务端资源,也没有结果游标,这与其余不少平台,如SQL,不同。