sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-1266) Sqoop2: Introduce top level commands
Date Mon, 13 Jan 2014 16:46:52 GMT

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

Jarek Jarcec Cecho updated SQOOP-1266:

    Attachment: SQOOP-1266.patch

> Sqoop2: Introduce top level commands
> ------------------------------------
>                 Key: SQOOP-1266
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1266
>             Project: Sqoop
>          Issue Type: Task
>    Affects Versions: 1.99.3
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.4
>         Attachments: SQOOP-1266.patch, SQOOP-1266.patch
> Currently we have in Sqoop 2 one command line utility {{sqoop.sh}} that is user suppose
to run with various arguments. As this shell script is not meant to be on the {{$PATH}}, we
have full path to the script on all documentation pages. This very confusing for downstream
consumption, as distributions such as BigTop are not exposing {{sqoop.sh}} script directly
and user is confused how to apply the instructions in the docs.
> I would like to propose top level commands similarly as we currently have in Sqoop 1
and use them in the documentation. This will lead to much cleaner documentation and as a side
effect our docs will be applicable to downstream distributions as well.

This message was sent by Atlassian JIRA

View raw message