Find a way to make users aware of indexing issues.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
Right now when indexing fails, it's hard for users to work out why find queries return nothing, or fewer results than expected. Think about ways to surface this (right now you need to run FT.INFO <index> and look at the output of that to see if there are failures / any documents in the index.
See #60 for an example of this occurring.
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 by reviewing how indexing failures are currently represented and how find queries behave when an index is empty or incomplete. Compare that with the failure and document counts exposed by FT.INFO, and read #60 for the reported example. Done requires an agreed way for users to discover indexing problems without manually inspecting FT.INFO.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, redis
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100