BetaOptional BetaaggregatesNumber of hits per limetype, keyed by limetype name.
The platform reports one count per limetype, so each entry holds a
single SearchHitCount: { company: [{ totalCount: 5 }] }.
A limetype that produced no hits is usually left out entirely rather than reported as zero, so treat a missing key as zero.
BetaobjectsObjects that matched the query, across every limetype searched.
Ordered by search score with the best match first, and capped by
SearchOptions.limit. Objects of different limetypes are mixed
together, so read _limetype to tell them apart.
These records carry _id, _limetype, _descriptive and the
properties covered by the search index, not the full object. Load the
object by id when you need the rest.
BetatotalTotal number of matching objects across every limetype that was counted.
Not capped by SearchOptions.limit, so this can exceed
objects.length. It is also wider than objects when hit counts cover
limetypes that were counted but not returned, so prefer the per-limetype
counts in aggregates when reporting on what came back.
Response from LimeObjectRepository.search.
Carries the matching objects and their total, plus the number of hits per limetype. This is not an ObjectResponse: search reports hit counts under
aggregatesrather than the aggregate calculations a query returns, and never carriestotalRelations.Example: Read the hit count for each limetype
See