blocks|key|38933|text|_count可能会更快一些，因为它不需要执行完整的查询并获取排名和结果，只需返回大小即可。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|38934|不过，更多地了解如何获得不同的结果将是一件有趣的事情。为此，我需要更多的信息，如您发送的确切查询，以及索引上是否正在进行任何索引。|38935|但假设您执行以下操作|38936|索引some+documents|38937|refresh+|unordered-list-item|38938|ordered-list-item|38939|38940|38941|_search和_count+(使用match+all查询)应返回相同的总数。如果不是，那就太奇怪了。|38942|entityMap^0|0|6|0|0|0|0|0|0|0|0|0|7|8|6|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|10|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|11|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|12|8|@]|D|@]|E|$]]|$1|O|3|-4|5|P|7|13|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|14|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|15|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|V|$]]

Probably <code>_count</code> is a bit faster since it doesn't have to execute a full query with ranking and result fetching and can simply return the size. 

It would be interesting to know a bit more about how you manage to get different results though. For that I need more information like what exact queries you are sending and if any indexing is going on on the index.

But suppose that you do the following

<ol>
<li>index some documents</li>
<li>refresh the index</li>
</ol>

<code>_search</code> and <code>_count</code> (with a match all query) should return the same total. If not, that'd be very weird.

blocks|key|38671|text|这两个查询提供了相同的结果，但：-+count消耗的资源/带宽更少，因为不需要获取文档、评分和其他内部优化。将搜索大小设置为0，可能非常相似。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|38672|如果您想计算索引中的所有记录，您还可以对"_type“字段执行聚合条件。|38673|结果应该是相同的。在比较结果之前，请确保执行索引刷新。|38674|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The two queries provide the same result but:
- count consumes less resources/bandwidth because doesn't require to fetch documents, scoring and other internal optimizations. Set the search size to 0, could be very similar.

If you want count all the record in an index, you can also execute an aggregation terms on "_type" field.

The results should be the same. Before comparing the results, be sure to execute an index refresh.

blocks|key|2719600|text|curl+http://localhost:9200/_cat/indices?v以表格形式向您提供计数和其他信息|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2719601|health+status+index++++++++++++++++++++++++++++++uuid+++++++++++++++++++pri+rep+docs.count+docs.deleted+store.size+pri.store.size
yellow+open+++logstash-2019.10.09-000001+++++++++IS7HBUgRRzO7Rn1puBFUIQ+++1+++1++++++++++0++++++++++++0+++++++283b+++++++++++283b
green++open+++.kibana_task_manager_1+++++++++++++e4zZcF9wSQGFHB_lzTszrg+++1+++0++++++++++2++++++++++++0+++++12.5kb+++++++++12.5kb
yellow+open+++metricbeat-7.4.0-2019.10.09-000001+h_CWzZHcRsakxgyC36-HTg+++1+++1+++++++6118++++++++++++0++++++2.2mb++++++++++2.2mb
green++open+++.apm-agent-configuration+++++++++++J6wkUr2CQAC5kF8-eX30jw+++1+++0++++++++++0++++++++++++0+++++++283b+++++++++++283b
green++open+++.kibana_2++++++++++++++++++++++++++W2ZETPygS8a83-Xcd6t44Q+++1+++0+++++++1836+++++++++++23++++++1.1mb++++++++++1.1mb
green++open+++.kibana_1++++++++++++++++++++++++++IrBlKqO0Swa6_HnVRYEwkQ+++1+++0++++++++++8++++++++++++0++++208.8kb++++++++208.8kb
yellow+open+++filebeat-7.4.0-2019.10.09-000001+++xSd2JdwVR1C9Ahz2SQV9NA+++1+++1++++++++++0++++++++++++0+++++++283b+++++++++++283b
green++open+++.tasks+++++++++++++++++++++++++++++0ZzzrOq0RguMhyIbYH_JKw+++1+++0++++++++++1++++++++++++0++++++6.3kb++++++++++6.3kb|code-block|syntax|javascript|2719602|entityMap^0|0|15|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

<code>curl http://localhost:9200/_cat/indices?v</code> provides you the count and other information in a tabular format

<pre><code>health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
yellow open logstash-2019.10.09-000001 IS7HBUgRRzO7Rn1puBFUIQ 1 1 0 0 283b 283b
green open .kibana_task_manager_1 e4zZcF9wSQGFHB_lzTszrg 1 0 2 0 12.5kb 12.5kb
yellow open metricbeat-7.4.0-2019.10.09-000001 h_CWzZHcRsakxgyC36-HTg 1 1 6118 0 2.2mb 2.2mb
green open .apm-agent-configuration J6wkUr2CQAC5kF8-eX30jw 1 0 0 0 283b 283b
green open .kibana_2 W2ZETPygS8a83-Xcd6t44Q 1 0 1836 23 1.1mb 1.1mb
green open .kibana_1 IrBlKqO0Swa6_HnVRYEwkQ 1 0 8 0 208.8kb 208.8kb
yellow open filebeat-7.4.0-2019.10.09-000001 xSd2JdwVR1C9Ahz2SQV9NA 1 1 0 0 283b 283b
green open .tasks 0ZzzrOq0RguMhyIbYH_JKw 1 0 1 0 6.3kb 6.3kb
</code></pre>

blocks|key|39216|text|老问题，插话，因为在ElasticSearch版本>+7.0上：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|39217|39218|_search：返回搜索查询命中计数小于或等于结果窗口大小的文档，结果窗口大小通常为10,000。例如：|ordered-list-item|offset|length|style|CODE|39219|39220|{“the”：3，"timed_out":false，"_shards":{"+total+":1，"successful":1，"skipped":0，"failed":0}，"+hits+":{"total":{"value":10000，"relation":"gte"}，"max_score"：0.34027478，the返回搜索查询的总命中数，而不考虑结果窗口的大小。未返回任何文档，例如：|39221|{“计数”：5703899，“总计”：{“_shards”：1，“成功”：1，“跳过”：0，“失败”：0}}|39222|因此，如果这是您配置的结果窗口大小，_search可能会返回总命中数为10,000，而_count将返回同一查询的实际计数。|39223|entityMap^0|0|0|0|7|0|0|0|0|I|7|17|6|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|U|8|@$F|V|G|W|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@$F|11|G|12|H|I]|$F|13|G|14|H|I]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|R|$]]

Old question, chipping in because on ElasticSearch version > 7.0 :

<ol>
<li><code>_search</code>: returns the documents with the hit count for the search query, less than or equal to the result window size, which is typically 10,000. e.g.:

{"took":3,"timed_out":false,"_shards":{"total":1,"successful":1,"skipped":0,"failed":0},"hits":{"total":{"value":10000,"relation":"gte"},"max_score": 0.34027478,"hits":[...]}}</li>
<li><code>_count</code>: returns the total number of hits for the search query irrespective of the result window size. no documents returned, e.g.:

{"count":5703899,"_shards":{"total":1,"successful":1,"skipped":0,"failed":0}}</li>
</ol>

So, <code>_search</code> might return the total hits as 10,000 if that is your configured result window size, while <code>_count</code> would return the actual count for the same query.

blocks|key|39992|text|如果必须使用_search而不是_count，并且您使用的是Elasticsearch+7.0%2B，则设置size:+0和track_total_hits:+true将提供与_count相同的信息|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|39993|GET+my-index/_search
{
++"query":+{+"term":+{+"field":+{+"value":+"xyz"+}+}+},
++"size":+0,
++"track_total_hits":+true
}


{
++"took"+:+612,
++"timed_out"+:+false,
++"_shards"+:+{
++++"total"+:+629,
++++"successful"+:+629,
++++"skipped"+:+524,
++++"failed"+:+0
++},
++"hits"+:+{
++++"total"+:+{
++++++"value"+:+29349466,
++++++"relation"+:+"eq"
++++},
++++"max_score"+:+null,
++++"hits"+:+[+]
++}
}|code-block|syntax|javascript|39994|请参阅Elasticsearch+7.0+Breaking+changes|39995|entityMap|0|LINK|mutability|MUTABLE|url|https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes-7.0.html#track-total-hits-10000-default^0|6|7|G|6|1G|7|1O|M|2E|6|0|0|3|Y|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|15|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|16|8|@]|D|@$9|17|A|18|1|19]]|E|$]]|$1|M|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

If <code>_search</code> must be used instead of <code>_count</code>, and you're on Elasticsearch 7.0+, setting <code>size: 0</code> and <code>track_total_hits: true</code> will provide the same info as <code>_count</code>

<pre><code>GET my-index/_search
{
 "query": { "term": { "field": { "value": "xyz" } } },
 "size": 0,
 "track_total_hits": true
}


{
 "took" : 612,
 "timed_out" : false,
 "_shards" : {
 "total" : 629,
 "successful" : 629,
 "skipped" : 524,
 "failed" : 0
 },
 "hits" : {
 "total" : {
 "value" : 29349466,
 "relation" : "eq"
 },
 "max_score" : null,
 "hits" : [ ]
 }
}
</code></pre>

See <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes-7.0.html#track-total-hits-10000-default" rel="noreferrer">Elasticsearch 7.0 Breaking changes</a>

If one wants to count the number of documents in an index (of Elasticsearch) then there are (at least?) two possibilities:

<ul>
<li>Direct <code>count</code>

POST my_index/_count

should return the number of documents in <code>my_index</code>.</li>
<li>Using <code>search</code>

Here one can use the <code>count</code> as the <code>search_type</code> or some other type. In either of the cases the total count can be extracted from the field <code>['hits']['total']</code></li>
</ul>

My questions are:

<ul>
<li>what is the difference between the different approaches? Which one
should I prefer?</li>
<li>I raise this question because I'm experiencing different results
depending on the chosen method. I'm now in the process of debugging
the issue, and this question popped up.</li>
</ul>

Counting number of documents using Elasticsearch

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

如果想要计算索引( Elasticsearch)中的文档数量，那么有(至少？)有两种可能性：Direct count发布my_index/_count应返回my_index.Using search中的文档数在这里，可以将count用作search_type或其他类型。在这两种情况下，总计数都可以从字段['hits']...

问使用Elasticsearch统计文档数
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Elasticsearch统计文档数EN