[
https://issues.apache.org/jira/browse/SQOOP-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Veena Basavaraj updated SQOOP-1498:
-----------------------------------
Description:
See the attached PDF.
Currently there is a lot of overlap with the entity model classes. All the
entity model classes in the code are are prefixed with "M" and are under the
org.apache.sqoop.model package.
The proposed refactoring will do the following things.
No more MConnectionForms and MJobForms
MConfig( abstract)
FromConfig ( may or may not inherit MConfigList). Still debating if we need a
conflg list. We can use a group attribute on the inputs if we need add
hierarchy to the config inputs
ToConfig
DriverConfig
FromConfig/ToConfig/DriverConfig entities belongs to a MJob
MInput (MConfig has one or more MInputs)
MConnector will be pretty dumb and will hold its 3 config objects, LinkConfig.
FromConfig and ToConfig
MLink belongs to a MConnector
MLink will have a reference to connector and the link config. There will be no
connector/ framework part.
MSubmisssion belongs to a MJob
Lastly, the Repository schema will also be renamed to reflect the
context/link/driver/jobrun changes
End of Story!
was:
See the attached PDF.
Currently there is a lot of overlap with the entity model classes. All the
entity model classes in the code are are prefixed with "M" and are under the
org.apache.sqoop.model package.
The proposed refactoring will do the following things.
No more MConnectionForms and MJobForms. The big different is the use of the
terminology context to hold all the job related information.
MContext ( abstract)
MFromContext
MToContext
MDriverContext
MContext entity belongs to a MJob
MInput (MContext has one or more MInputs)
MJob has MFromContext, MToContext, MDriverContext
MConnector ( Connector has one or more links)
MLink belongs to a MConnector
MJobRun belongs to a MJob ( Job has one or more JobRuns)
Lastly, the Repository schema will also be renamed to reflect the
context/link/driver/jobrun changes
End of Story!
> Sqoop2: Sqoop2 Job Repository Object refactoring ( objects prefixed with M)
> ---------------------------------------------------------------------------
>
> Key: SQOOP-1498
> URL: https://issues.apache.org/jira/browse/SQOOP-1498
> Project: Sqoop
> Issue Type: Improvement
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Attachments: Sqoop2.pdf
>
>
> See the attached PDF.
> Currently there is a lot of overlap with the entity model classes. All the
> entity model classes in the code are are prefixed with "M" and are under the
> org.apache.sqoop.model package.
> The proposed refactoring will do the following things.
> No more MConnectionForms and MJobForms
> MConfig( abstract)
> FromConfig ( may or may not inherit MConfigList). Still debating if we need a
> conflg list. We can use a group attribute on the inputs if we need add
> hierarchy to the config inputs
> ToConfig
> DriverConfig
> FromConfig/ToConfig/DriverConfig entities belongs to a MJob
> MInput (MConfig has one or more MInputs)
> MConnector will be pretty dumb and will hold its 3 config objects,
> LinkConfig. FromConfig and ToConfig
> MLink belongs to a MConnector
> MLink will have a reference to connector and the link config. There will be
> no connector/ framework part.
> MSubmisssion belongs to a MJob
> Lastly, the Repository schema will also be renamed to reflect the
> context/link/driver/jobrun changes
> End of Story!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
