-
Notifications
You must be signed in to change notification settings - Fork 332
fix(search): Make adding events to index idempotent. #5567
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
c8b58c5
to
5ea9850
Compare
CodSpeed Performance ReportMerging #5567 will not alter performanceComparing Summary
|
0aa4376
to
010e2a7
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5567 +/- ##
==========================================
- Coverage 88.63% 88.62% -0.01%
==========================================
Files 341 341
Lines 95138 95196 +58
Branches 95138 95196 +58
==========================================
+ Hits 84322 84371 +49
+ Misses 6628 6625 -3
- Partials 4188 4200 +12 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Slightly worried that we have to run a specific search for what's conceptually a set lookup. Could you write a tiny benchmark and measure how long it takes to add the same document, say, 1000 / 10000 / 100000 times? (not necessarily one in the benches
dir and that we'd check in, but you'd get bonus points for that!)
010e2a7
to
59be73d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please look at my previous review comment where I asked for running a tiny benchmark.
Adding events to the index is now idempotent.
Signed-off-by: Shrey Patel [email protected]