-
Notifications
You must be signed in to change notification settings - Fork 1.4k
add /tasks/{taskType}/{tableNameWithType}/debug API #8949
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
add /tasks/{taskType}/{tableNameWithType}/debug API #8949
Conversation
Codecov Report
@@ Coverage Diff @@
## master #8949 +/- ##
============================================
- Coverage 69.69% 66.26% -3.43%
+ Complexity 4715 4695 -20
============================================
Files 1813 1361 -452
Lines 94503 68700 -25803
Branches 14117 10746 -3371
============================================
- Hits 65860 45523 -20337
+ Misses 24039 19899 -4140
+ Partials 4604 3278 -1326
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
| String tableNameWithType, | ||
| @ApiParam(value = "verbosity (By default, prints for running and error tasks. Value of >0 prints for all tasks)") | ||
| @DefaultValue("0") @QueryParam("verbosity") int verbosity) { | ||
| return _pinotHelixTaskResourceManager.getTasksDebugInfoByTable(taskType, tableNameWithType, verbosity); |
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.
I tried this out with RealtimeQuickstartWithMinion, and saw it return 3 COMPLETED tasks, for both 0 and 1 verbosity. Only difference was level of detail. Is this By default, prints for running and error tasks. Value of >0 prints for all tasks) incorrect or does the impl need some change?
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.
simply copied and pasted the existing docs 😄 . fixed this one and existing ones.
| String tableNameConfig = pinotConfigs.get(TABLE_NAME); | ||
| if (tableNameConfig != null && tableNameConfig.equals(tableNameWithType)) { | ||
| // Found a match. Add task debug info to the result | ||
| // TODO: we may want to filter out debug info that does not belong to the given table. |
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.
didn't follow this TODO. why would we get info from getTaskDebugInfo that's not for this table?
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.
updated the TODO.
Mind adding a sample response here? |
|
Sample response when verbosity = 0
|
|
Sample response when verbosity = 1
|
What Does This PR Do
Add /tasks/{taskType}/{tableNameWithType}/debug API so that we can get a task debug info for the given table. This makes debugging a specific table's problem easier.
Test
Test by setting up a Pinot cluster locally.