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

Implement Store Job Result Controller #3515

Closed
pranavsid98 opened this issue Jun 7, 2017 · 2 comments
Closed

Implement Store Job Result Controller #3515

pranavsid98 opened this issue Jun 7, 2017 · 2 comments
Assignees

Comments

@pranavsid98
Copy link
Contributor

pranavsid98 commented Jun 7, 2017

This implements Milestone 3 of the VM project.

This controller is used by the VM to store the result of the training job. It needs to do the following things in sequence:

  1. Validate the incoming request by calling “validate_request(request_data)” method. If request is valid the proceed ahead otherwise return error code 401 (Unauthorized access).
  2. Extract job_request_id, classifier_data from incoming request.
  3. Find “ClassifierTrainingJobModel” corresponding to job_request_id. Extract state_name, exp_id, algorithm_id, exp_version from this model.
  4. Find classifier_model_id stored in corresponding state. If it is not available then Create new “Classifier Data Model” instance with id = job_request_id.
  5. Set exp_id, exp_version, state_name, algorithm_id and classifier_data in model instance. Store model instance in database.
  6. Set the classifier_model_id of state to ID of this Classifier Data Model instance.
  7. Modify job request model’s status to indicate that job has been finished. Store it back to database.

/cc @anmolshkl @prasanna08

@pranavsid98
Copy link
Contributor Author

This can be started after the storage/domain layers are implemented. I'll take this controller issue up.

@prasanna08
Copy link
Contributor

prasanna08 commented Jun 10, 2017

@pranavsid98 make sure that URLs for these controllers are same as the once described in this doc. It would be better to define them in feconf.py as constants.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants