Skip to content
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

[YUNIKORN-2652] Add Resource Usage details to getApplication endpoint #892

Closed

Conversation

richscott
Copy link
Contributor

What is this PR for?

These changes enhance the getApplication() function in pkg/webservice/ to include some additional fields that may be valuable to users viewing completed applications - specifically, the response now included StartTime, ResourceUsage, PreemptedResource, and PlaceholderResource members.

What type of PR is it?

  • - Bug Fix
  • - Improvement
  • - Feature
  • - Documentation
  • - Hot Fix
  • - Refactoring

Todos

  • - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/YUNIKORN-2652

How should this be tested?

Any request to the endpoint(s) that use the getApplication() function can be queried, with an additional boolean query parameter of details set to true, e.g.

$ curl --silent 'http://localhost:9889/ws/v1/partition/default/queue/root.default/application/app-1?details=true' | jq

Add logic to the getApplication webservice handler to provide expanded
details about an application, including resource usage, if the
`details=true` query parameter is specified on the endpoint request.
Add logic to the getApplication webservice handler to provide expanded
details about an application, including resource usage, if the
`details=true` query parameter is specified on the endpoint request.
…yunikorn-core into getapplication-resource-usage
Add logic to the getApplication webservice handler to provide expanded
details about an application, including resource usage, if the
`details=true` query parameter is specified on the endpoint request.
…yunikorn-core into getapplication-resource-usage
Add logic to the getApplication webservice handler to provide expanded
details about an application, including resource usage, if the
`details=true` query parameter is specified on the endpoint request.
…yunikorn-core into getapplication-resource-usage
Copy link

codecov bot commented Jun 18, 2024

Codecov Report

Attention: Patch coverage is 5.26316% with 36 lines in your changes missing coverage. Please review.

Project coverage is 78.31%. Comparing base (87b1d7c) to head (abeb81e).

Files Patch % Lines
pkg/webservice/handlers.go 5.26% 34 Missing and 2 partials ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #892      +/-   ##
==========================================
- Coverage   78.52%   78.31%   -0.22%     
==========================================
  Files          97       97              
  Lines       12206    12241      +35     
==========================================
+ Hits         9585     9586       +1     
- Misses       2323     2356      +33     
- Partials      298      299       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@pbacsko pbacsko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please enhance the unit tests to ensure proper coverage.

@pbacsko
Copy link
Contributor

pbacsko commented Jul 2, 2024

@richscott should this PR be closed and we continue with #897 ?

@richscott
Copy link
Contributor Author

@richscott should this PR be closed and we continue with #897 ?

I was out on holiday for the last two weeks - this other PR (#897) looks like it would work fine, I will close this PR. Thanks.

@richscott richscott closed this Jul 2, 2024
@richscott richscott deleted the getapplication-resource-usage branch July 2, 2024 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants