sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Veena Basavaraj (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-1681) DOC: Create an API doc for the Sqoop Execution engine ( since its extensible)
Date Wed, 05 Nov 2014 18:24:34 GMT

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

Veena Basavaraj updated SQOOP-1681:
-----------------------------------
    Description: 
Having a good doc for repository will encourage us to create better code going forward to
support other types of  execution and submission engines.

The do and donts of the apis and the responsibilities of the engine needs to be documented.
This can extend to a bit more than JUST java doc. Some details on the design would be helpful
too! Similar thoughts as I suggested for the repo api.

Going forward we should encourage running sqoop on TEZ as well.  Just kidding.


  was:
Having a good doc for repository will encourage us to create better code going forward to
support other types of  execution and submission engines.

The do and donts of the apis and the responsibilities of the engine needs to be documented.
This can extend to a bit more than jsut java doc. Some details on the design would be helpful
too!

Similar thoughts as repo api.

Going forward we should encourage running sqoop on TEZ as well.  Just kidding.



> DOC: Create an API doc for the Sqoop Execution engine ( since its extensible)
> -----------------------------------------------------------------------------
>
>                 Key: SQOOP-1681
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1681
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: Veena Basavaraj
>            Assignee: Veena Basavaraj
>             Fix For: 1.99.5
>
>
> Having a good doc for repository will encourage us to create better code going forward
to support other types of  execution and submission engines.
> The do and donts of the apis and the responsibilities of the engine needs to be documented.
This can extend to a bit more than JUST java doc. Some details on the design would be helpful
too! Similar thoughts as I suggested for the repo api.
> Going forward we should encourage running sqoop on TEZ as well.  Just kidding.



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

Mime
View raw message