Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sqoop.apache.org
Date: Fri, 3 Oct 2014 06:53:34 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: dev@sqoop.apache.org
Message-ID: <JIRA.12740158.1410275731000.182391.1412319214481@Atlassian.JIRA>
In-Reply-To: <JIRA.12740158.1410275731000@Atlassian.JIRA>
References: <JIRA.12740158.1410275731000@Atlassian.JIRA>
 <JIRA.12740158.1410275731295@arcas>
Subject: [jira] [Commented] (SQOOP-1498) Sqoop2: Repository Object
 refactoring ( objects prefixed with M)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SQOOP-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157742#comment-14157742 ] 

ASF subversion and git services commented on SQOOP-1498:
--------------------------------------------------------

Commit f63c080dd6b20c8c5848d930aeb8cce204cc702d in sqoop's branch refs/heads/SQOOP-1367 from [~abec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=f63c080 ]

SQOOP-1498: Sqoop2: Repository Object refactoring (objects prefixed with M)

(Veena Basavaraj via Abraham Elmahrek)


> Sqoop2: 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: SQOOP-1498final.patch, SQOOP-1498finalwithoutgitignore.patch, 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)