typesense / typesense/typesense
Documentation/Clarification on Analytics Limit Rule beyond limit
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.6k
- Forks
- 973
- Avg merge
- 18h 45m
- Merged PRs (30d)
- 4
Description
Description
What happens when the limit is reached?
For example:
We hit the analytics collection limit of 1000,
Each query now has count > 2
What happens to new queries?
- New queries are ignored unless >2 searches occur within the
analytics-flush-interval - New queries are retained regardless and added to the collection when they are within the top 1000.
Metadata
Typesense Version: 0.27.1
OS: Ubuntu 22.04
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 analytics limit behavior described for Typesense 0.27.1 and determine which of the two outcomes applies when the collection reaches 1000 entries. Document the confirmed behavior, including how new queries and the analytics-flush-interval interact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- analytics, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100