You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Veena Basavaraj (JIRA)" <ji...@apache.org> on 2014/10/23 02:59:34 UTC

[jira] [Updated] (SQOOP-1497) Sqoop2: Sqoop2 Entity Nomenclature Revisited

     [ https://issues.apache.org/jira/browse/SQOOP-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Veena Basavaraj updated SQOOP-1497:
-----------------------------------
    Affects Version/s: 1.99.4

> Sqoop2: Sqoop2 Entity Nomenclature Revisited
> --------------------------------------------
>
>                 Key: SQOOP-1497
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1497
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.99.4
>            Reporter: Veena Basavaraj
>            Assignee: Veena Basavaraj
>             Fix For: from/to
>
>         Attachments: Connector-Link-Config-Job-Driver.pdf, SQOOP-1497afterRebase.patch, SimplifySqoopEntityNomenclature.pdf
>
>
> See the attached PDF.
> Naming Entities is as important as the functionality :). In sqoop2, we have evolved Sqoop to support a lot more things and it is good to reconsider /revisit the entity nomenclature we currently have



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)