Closed nicolastoulemont closed 2 weeks ago
/bounty 75
/attempt #730
with your implementation plan/claim #730
in the PR body to claim the bountyThank you for contributing to askorama/orama!
Add a bounty • Share on socials
Attempt | Started (GMT+0) | Solution |
---|---|---|
🟢 @abhishek818 | Jun 6, 2024, 1:17:42 AM | #732 |
🟢 @rajeshj11 | Jun 6, 2024, 10:31:50 AM | #731 |
/attempt #730
Algora profile | Completed bounties | Tech | Active attempts | Options |
---|---|---|---|---|
@abhishek818 | 4 bounties from 3 projects | JavaScript, TypeScript |
Cancel attempt |
/attempt #730
Algora profile | Completed bounties | Tech | Active attempts | Options |
---|---|---|---|---|
@rajeshj11 | 4 bounties from 3 projects | JavaScript, TypeScript, HTML |
Cancel attempt |
💡 @rajeshj11 submitted a pull request that claims the bounty. You can visit your bounty board to reward.
🎉🎈 @rajeshj11 has been awarded $75! 🎈🎊
Describe the bug
Using the hybrid search with a where clause and a offset + a limit has two issues:
To Reproduce
You can find a codesandbox with the issue here
More details on the issue on slack here
TLDR: The issue is due to pagination being apply twice with the hybrid search call-stack both on the uniqueTokenScores and within the fetchDocuments function.
Expected behavior
Correct document fetching and correct count values.
Environment Info
Affected areas
Search
Additional context
No response