[
https://issues.apache.org/jira/browse/OOZIE-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927421#comment-15927421
]
ASF GitHub Bot commented on OOZIE-2816:
---------------------------------------
GitHub user QwertyManiac opened a pull request:
https://github.com/apache/oozie/pull/26
OOZIE-2816 Strip out the first command word from Sqoop action if its …
…"sqoop" (harsh)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/QwertyManiac/apache-oozie OOZIE-2816
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/oozie/pull/26.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #26
----
commit 83222159f774341d3bcf32a140bd1d5f54bbf208
Author: Harsh J <[email protected]>
Date: 2017-03-09T13:00:17Z
OOZIE-2816 Strip out the first command word from Sqoop action if its
"sqoop" (harsh)
----
> Strip out the first command word from Sqoop action if its "sqoop"
> -----------------------------------------------------------------
>
> Key: OOZIE-2816
> URL: https://issues.apache.org/jira/browse/OOZIE-2816
> Project: Oozie
> Issue Type: Bug
> Components: action
> Affects Versions: 4.3.0
> Reporter: Harsh J
> Assignee: Harsh J
> Priority: Trivial
> Attachments: OOZIE-2816.000.patch, OOZIE-2816.001.patch
>
>
> A [sorta
> popular|https://www.google.com/search?q=%22No+such+sqoop+tool:+sqoop%22+oozie&*]
> user error is to specify the command part of the sqoop action in the style
> of the CLI: "sqoop import …" instead of just the required "import …". This
> causes the Sqoop action to predictably fail with:
> {code}
> No such sqoop tool: sqoop. See 'sqoop help'.
> Intercepting System.exit(1)
> {code}
> A simple enhancement can prevent this burden on user. We can skip the first
> command token if its "sqoop".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
