public/seasearch-docs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update search_document.md

Browse source
This commit is contained in:
Kaniu 2025-02-28 15:44:54 +08:00 • committed by GitHub
parent 32954db599
commit f182444eb6
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
manual/api/search_document.md
View file

@ -25,7 +25,7 @@ ElasticSearch API: [Multi-Search API Documentation](https://www.elastic.co/guide
```
### Unified-Search
The original search API (/es/_search) already supports searching a single index or multiple indexes. In Elasticsearch, the search-type parameter [ES Search Type](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/search-search.html#search-type) controls whether the results from multiple indexes are scored uniformly. We simplified this by using a unified scoring mechanism for all results. Therefore, this API can support both unified scoring of results from multiple indexes and parallel querying of large indexes under clustering. The difference with our custom unified_search API is that it only has one query object, so it doesn't support using different filters for different indexes.
The original search API (/es/_search) already supports searching a single index or multiple indexes. In Elasticsearch, the [search-type parameter](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/search-search.html#search-type) controls whether the results from multiple indexes are scored uniformly. We simplified this by using a unified scoring mechanism for all results. Therefore, this API can support both unified scoring of results from multiple indexes and parallel querying of large indexes under clustering. The difference with our custom unified_search API is that it only has one query object, so it doesn't support using different filters for different indexes.
This API is meaningful only in this scenario: when searching the same query across multiple indexes. For example, in Seafile, we create an index for each library. When globally searching across all accessible libraries, using this API ensures consistent scoring across different repositories, providing more accurate search results.