You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Whether certain properties of the search response are calculated exhaustive (exact) or approximated.
87
+
*
88
+
* List of fields:
89
+
*
90
+
* `facetsCount`: Whether the facet count is exhaustive (true) or approximate (false). See the [related discussion](https://support.algolia.com/hc/en-us/articles/4406975248145-Why-are-my-facet-and-hit-counts-not-accurate-).
91
+
* `facetValues`: The value is false if not all facet values are retrieved.
92
+
* `nbHits`: Whether the `nbHits` is exhaustive (true) or approximate (false). When the query takes more than 50ms to be processed, the engine makes an approximation. This can happen when using complex filters on millions of records, when typo-tolerance was not exhaustive, or when enough hits have been retrieved (for example, after the engine finds 10,000 exact matches). `nbHits` is reported as non-exhaustive whenever an approximation is made, even if the approximation didn't, in the end, impact the exhaustiveness of the query.
93
+
* `rulesMatch`: Rules matching exhaustiveness. The value is false if rules were enabled for this query, and could not be fully processed due a timeout. This is generally caused by the number of alternatives (such as typos) which is too large.
94
+
* `typo`: Whether the `typo` search was exhaustive (true) or approximate (false). An approximation is done when the typo search query part takes more than 10% of the query budget (i.e., 5ms by default) to be processed (this can happen when a lot of typo alternatives exist for the query). This field will not be included when typo-tolerance is entirely disabled.
* An echo of the query text. See the [Query.query] search parameter.
81
99
*/
@@ -285,6 +303,9 @@ public data class ResponseSearch(
285
303
*
286
304
* @throws IllegalStateException if [exhaustiveNbHitsOrNull] is null
287
305
*/
306
+
@Deprecated("See the `nbHits` field of the `exhaustive` object in the response.",
307
+
ReplaceWith("exhaustive.nbHits")
308
+
)
288
309
publicval exhaustiveNbHits:Boolean
289
310
get() = checkNotNull(exhaustiveNbHitsOrNull)
290
311
@@ -294,9 +315,26 @@ public data class ResponseSearch(
294
315
*
295
316
* @throws IllegalStateException if [exhaustiveFacetsCountOrNull] is null
296
317
*/
318
+
@Deprecated("See the `facetsCount` field of the `exhaustive` object in the response.",
319
+
ReplaceWith("exhaustive.facetsCount")
320
+
)
297
321
publicval exhaustiveFacetsCount:Boolean
298
322
get() = checkNotNull(exhaustiveFacetsCountOrNull)
299
323
324
+
/**
325
+
* Whether certain properties of the search response are calculated exhaustive (exact) or approximated.
326
+
*
327
+
* List of fields:
328
+
*
329
+
* `facetsCount`: Whether the facet count is exhaustive (true) or approximate (false). See the [related discussion](https://support.algolia.com/hc/en-us/articles/4406975248145-Why-are-my-facet-and-hit-counts-not-accurate-).
330
+
* `facetValues`: The value is false if not all facet values are retrieved.
331
+
* `nbHits`: Whether the `nbHits` is exhaustive (true) or approximate (false). When the query takes more than 50ms to be processed, the engine makes an approximation. This can happen when using complex filters on millions of records, when typo-tolerance was not exhaustive, or when enough hits have been retrieved (for example, after the engine finds 10,000 exact matches). `nbHits` is reported as non-exhaustive whenever an approximation is made, even if the approximation didn't, in the end, impact the exhaustiveness of the query.
332
+
* `rulesMatch`: Rules matching exhaustiveness. The value is false if rules were enabled for this query, and could not be fully processed due a timeout. This is generally caused by the number of alternatives (such as typos) which is too large.
333
+
* `typo`: Whether the `typo` search was exhaustive (true) or approximate (false). An approximation is done when the typo search query part takes more than 10% of the query budget (i.e., 5ms by default) to be processed (this can happen when a lot of typo alternatives exist for the query). This field will not be included when typo-tolerance is entirely disabled.
334
+
*/
335
+
publicval exhaustive:Exhaustive
336
+
get() = checkNotNull(exhaustiveOrNull)
337
+
300
338
/**
301
339
* An echo of the query text. See the [Query.query] search parameter.
* Whether certain properties of the search response are calculated exhaustive (exact) or approximated.
9
+
*
10
+
* List of fields:
11
+
*
12
+
* `facetsCount`: Whether the facet count is exhaustive (true) or approximate (false). See the [related discussion](https://support.algolia.com/hc/en-us/articles/4406975248145-Why-are-my-facet-and-hit-counts-not-accurate-).
13
+
* `facetValues`: The value is false if not all facet values are retrieved.
14
+
* `nbHits`: Whether the `nbHits` is exhaustive (true) or approximate (false). When the query takes more than 50ms to be processed, the engine makes an approximation. This can happen when using complex filters on millions of records, when typo-tolerance was not exhaustive, or when enough hits have been retrieved (for example, after the engine finds 10,000 exact matches). `nbHits` is reported as non-exhaustive whenever an approximation is made, even if the approximation didn't, in the end, impact the exhaustiveness of the query.
15
+
* `rulesMatch`: Rules matching exhaustiveness. The value is false if rules were enabled for this query, and could not be fully processed due a timeout. This is generally caused by the number of alternatives (such as typos) which is too large.
16
+
* `typo`: Whether the `typo` search was exhaustive (true) or approximate (false). An approximation is done when the typo search query part takes more than 10% of the query budget (i.e., 5ms by default) to be processed (this can happen when a lot of typo alternatives exist for the query). This field will not be included when typo-tolerance is entirely disabled.
0 commit comments