[
https://issues.apache.org/jira/browse/SQOOP-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136078#comment-14136078
]
Veena Basavaraj commented on SQOOP-1497:
----------------------------------------
The final reviews for this ticket propose the following ( includes renaming
the apis, the shell/client code, the model objects and the the tables in the
derby repository schema). I might be missing other places at this point
1. rename framework to driver
2. rename the connection to link
3. rename all the forms to configs ( both on the connection and job side ) i.e
from the rest apis for jobs and also in the connector apis.
4. rename metadata to repository
Leave Submission and Submission engine as it is. Submission becomes read-only
resource ( See SQOOP-1509)
> Sqoop2: Sqoop2 Entity Nomenclature Revisited
> --------------------------------------------
>
> Key: SQOOP-1497
> URL: https://issues.apache.org/jira/browse/SQOOP-1497
> Project: Sqoop
> Issue Type: Improvement
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Attachments: 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)
