-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fixing requestId generator bug in PinotBrokerDebug Resource #13716
Conversation
pinot-broker/src/main/java/org/apache/pinot/broker/api/resources/PinotBrokerDebug.java
Outdated
Show resolved
Hide resolved
464b7ab
to
a137615
Compare
pinot-broker/src/main/java/org/apache/pinot/broker/api/resources/PinotBrokerDebug.java
Outdated
Show resolved
Hide resolved
a137615
to
7c50669
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.
Thanks for fixing this. Would be great to add a test to ensure that the api doesn't always return the exact same routing table across calls.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #13716 +/- ##
============================================
+ Coverage 61.75% 61.99% +0.24%
+ Complexity 207 198 -9
============================================
Files 2436 2554 +118
Lines 133233 140661 +7428
Branches 20636 21880 +1244
============================================
+ Hits 82274 87205 +4931
- Misses 44911 46824 +1913
- Partials 6048 6632 +584
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Are we going to create a new class for each http request? That is surprising |
The issue here is that
_requestIdGenerator
is local to the HttpResource and will be created for every http request, so the requestId is always 0.