typesense / typesense/typesense
[Feature Request] Filter Caching
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.6k
- Forks
- 973
- Avg merge
- 18h 45m
- Merged PRs (30d)
- 4
Description
Description
The ability to either manually specify cached filters or for TypeSense to do it automatically (similar to elasticsearch)
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 the existing filter-processing and caching design in Typesense, then clarify whether caching should be manually configured, automatic, or both. Define the supported filter cases, cache behavior, invalidation rules, and acceptance criteria before implementation; no files or tests are identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100