Skip to content
This repository was archived by the owner on Mar 21, 2024. It is now read-only.

Commit ba3c2e7

Browse files
committed
Add variant message to ensure _geoPoint and _geoRadius expressions are not used as a ranking rule to help the user (#78)
1 parent de32a1b commit ba3c2e7

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

text/0059-geo-search.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -245,7 +245,8 @@ This error is raised asynchronously when the user tries to specify an invalid ra
245245

246246
- 🔴 Specifying an invalid ranking rule name raises an `invalid_ranking_rule` error. See `message` defined in the error definition part.
247247
- 🔴 Specifying a custom ranking rule with `_geo` or `_geoDistance` raises an `invalid_ranking_rule` error. The message is `:reservedKeyword is a reserved keyword and thus can't be used as a ranking rule.`.
248-
248+
- 🔴 Specifying a custom ranking rule with `_geoPoint` raises an `invalid_ranking_rule` error. The message is `_geoPoint is a reserved keyword and thus can't be used as a ranking rule. _geoPoint can only be used for sorting at search time`.
249+
- 🔴 Specifying a custom ranking rule with `_geoRadius` raises an `invalid_ranking_rule` error. The message is `_geoRadius is a reserved keyword and thus can't be used as a ranking rule. _geoRadius can only be used for filtering at search time`.
249250
---
250251

251252
### IV. Finalized Key Changes

0 commit comments

Comments
 (0)