Veena Basavaraj created SQOOP-1496:
--------------------------------------
Summary: Sqoop2: Revisit/Refactor the
SubmissionEngine/ExecutionEngine APIs
Key: SQOOP-1496
URL: https://issues.apache.org/jira/browse/SQOOP-1496
Project: Sqoop
Issue Type: Improvement
Reporter: Veena Basavaraj
Assignee: Veena Basavaraj
Here are the things this ticket should address
1. Refactor the submit() in JobManager ( it is way too long for any good unit
testing to happen)
2. Revisit the Execution Engine and Submission Engine relationship in the code.
ExecutionEngine api should probably not create a submissionRequest. It should
be the inverse. The Submission Engine is an abstraction of a JobTracker/ YARN/
Mesos/ OOzie. It will create a execution request for the execution engine while
it manages the job
a) Suggest renaming SubmissionEngine to a JobSubmissionManager
b) SubmissionRequest is a JobExecutionRequest
c) Change the apis in Execution Engine/ SubmissionManager to reflect the same
d) The Submission term is overloaded in the code base. In one case it is used
to represent the JobRuns( history of the jobs) and in another place it is the
submission engine such as JobTracker/YARN/ OOzie. These are unrelated and we
should not be overloading this term in Sqoop
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
