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
Improve SchedulerClient compliance with Scheduler API #2736
Conversation
fviale
commented
Nov 27, 2016
- improve the handling of job and task results handling, to allow transparent navigation (job to task, logs, etc). Added correct dozer mappings for job and task results
- improve the handling of job info and corrected the metrics which were broken in both Java and Rest apis
- implemented a few previously unsupported methods in SchedulerClient class
- better handling of the task logs and exception in Task result
- Added a test in SchedulerClientTest to test a few accesses to the scheduler api, mostly job result but also job state, job info
synchronize fork
synchronize fork
synchronize fork
- improve the handling of job and task results handling, to allow transparent navigation (job to task, logs, etc). Added correct dozer mappings for job and task results - improve the handling of job info and corrected the metrics which were broken in both Java and Rest apis - implemented a few previously unsupported methods in SchedulerClient class - better handling of the task logs and exception in Task result - Added a test in SchedulerClientTest to test a few accesses to the scheduler api, mostly job result but also job state, job info
- fixing unit tests
…into ow2-proactive-master
throw new UnsupportedOperationException(); | ||
Map<String, TaskStateData> taskStateMap = jobStateData.getTasks(); | ||
Map<TaskId, TaskState> hmTasks = new HashMap<>(); | ||
for (TaskStateData ts : taskStateMap.values()) { |
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.
can you call ts "taskStateData" ?
@@ -68,7 +70,13 @@ private void copyGenericInformation(JobStateData jobStateData) { | |||
|
|||
@Override | |||
public Map<TaskId, TaskState> getHMTasks() { | |||
throw new UnsupportedOperationException(); | |||
Map<String, TaskStateData> taskStateMap = jobStateData.getTasks(); | |||
Map<TaskId, TaskState> hmTasks = new HashMap<>(); |
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.
can you give a better name to hmTasks ?
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.
looks ok to me, some naming to refactor, but seems fine. Have you tried to run all the system tests against your local scheduler with these changes?
SonarQube analysis reported 5 issues
|