Briefly, this error occurs when Elasticsearch cannot find the specified ID in the source document. This could be due to a missing or incorrect ID field in the document. To resolve this issue, you can check the document to ensure the ID field is present and correctly named. If the ID field is missing, you need to add it. If it’s incorrectly named, you need to rename it. Also, ensure that the ID value is unique and correctly formatted.
This guide will help you check for common problems that cause the log ” -> id [{}]; _source [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: aggregations.
Aggregation in Elasticsearch
Overview
In Elasticsearch an aggregation is a collection or the gathering of related things together. The aggregation framework collects all the data based on the documents that match a search request which helps in building summaries of the data. Unlike Elasticsearch facets, aggregations can be nested. So aggregations can have sub-aggregations that operated on the documents which are generated by parent aggregation. Below are the different types of aggregations, each aggregation has its own purpose:
Metrics Aggregations: Metric Aggregation mainly refers to the mathematical calculations performed on the documents present in the bucket based upon given search criteria. For example, if you choose a number field; then the metric calculations you can perform on it are COUNT, SUM, MIN, MAX, AVERAGE etc.
Bucket Aggregations: Bucket aggregations create buckets or sets of documents based on given criteria in query. When the aggregation is performed, the documents are placed in the respective bucket, at the end we get a list of buckets, each with a list of documents. Example of bucket aggregation is Histogram Aggregation, Range Aggregation, Terms Aggregation, Filter(s) Aggregations, Geo Distance Aggregation and IP Range Aggregation.
Pipeline Aggregations: These aggregations allow you to aggregate over the result of another aggregation rather than from document sets.
Matrix Aggregations: Unlike Metric and Bucket aggregations, this aggregation work on more than one field and produce a matrix result based on the values from the requested document fields.
Examples
This aggregation is used to get the average of any numeric field present in the aggregated documents. For example below query computes the average fees over all documents
POST /schools/_search
{
"aggs":{
"avg_fees":{"avg":{"field":"fees"}}
}
}In query “aggs” object holds the aggregation to be computed. “avg_fees” is the name of the aggregation, “avg_fees” can be referred in scripts also and “avg” is the type of aggregation applied on fees field. The above will return the following:
{
...
"aggregations" : {
"avg_fees" : {
"value" : 2650.0
}
}
}Log Context
Log “-> id [{}]; _source [{}]” classname is tophits-aggregation.asciidoc.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
logger.info("key [{}]; doc_count [{}]"; key; docCount);
// We ask for top_hits for each bucket
TopHits topHits = entry.getAggregations().get("top");
for (SearchHit hit : topHits.getHits().getHits()) {
logger.info(" -> id [{}]; _source [{}]"; hit.getId(); hit.getSourceAsString());
}
}
--------------------------------------------------
This will basically produce for the first example:
[ratemypost]
