sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sqoop QA bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1266) Sqoop2: Introduce top level commands
Date Mon, 13 Jan 2014 16:54:51 GMT

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

Sqoop QA bot commented on SQOOP-1266:
-------------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12622654/SQOOP-1266.patch against branch
sqoop2.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} failed to build with patch (exit code 1)
{color:red}ERROR:{color} Patch does not add/modifny any test case
{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly

Console output: https://builds.apache.org/job/PreCommit-SQOOP-Build/216/console

This message is automatically generated.

> 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
(v6.1.5#6160)

Mime
View raw message