generally, RangeKeys() not supportable in Mad-Hatter
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I think, generally, RangeKeys() are not supportable in Mad-Hatter, since the query engine assumes an ordering to the keys?
https://github.com/couchbase/n1fty/blob/7b74840ba11976e200eeecb98eb1c53081441876/index.go#L89
Contributor guide
No contributing guide indexed for this repository
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 by reading index.go around line 89 and trace how RangeKeys() is handled by the Mad-Hatter query engine. Determine whether key ordering is an inherent limitation or a support gap; the issue is complete only when the supported behavior and any required change are clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100