Support GEOFILTER argument for FT.SEARCH
Open
Nobody has claimed this yet.
feature
stale
- Dominant language
- TypeScript
- Stars
- 17.6k
- Forks
- 2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 40
Description
This search option can be utilized with the client.sendCommand(...) method but I would love to see it natively supported. Here is the argument spec:
FT.SEARCH ... GEOFILTER {geo_attribute} {lon} {lat} {radius} m|km|mi|ft
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the client.sendCommand(...) entry point and locate how FT.SEARCH arguments are represented and tested. Compare that handling with the supplied GEOFILTER specification; done means native FT.SEARCH support accepts the geo attribute, coordinates, radius, and listed units without requiring a raw command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis, typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 67/100