[
https://issues.apache.org/jira/browse/OOZIE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068714#comment-16068714
]
Peter Cseh edited comment on OOZIE-2949 at 6/29/17 6:00 PM:
------------------------------------------------------------
We got most of the user complaints when they are using the --query tag and then
proceeded to copy-paste the command line into oozie.
Something like
{code}
sqoop import --connect jdbc:mysql://example.com:3306/test --username new_user
--password pwdpwd --m 1 --query 'SELECT * FROM employee' --target-dir
/user/new_user/employee4 --verbose
{code}
was (Author: gezapeti):
We got most of the user complaints when they are using the --query tag and then
proceeded to copy-paste the command line into oozie.
Something like
{noformat}
sqoop import --connect jdbc:mysql://example.com:3306/test --username new_user
--password pwdpwd --m 1 --query 'SELECT * FROM employee' --target-dir
/user/new_user/employee4 --verbose
{noformat}
> Escape quotes whitespaces in Sqoop <command> field
> --------------------------------------------------
>
> Key: OOZIE-2949
> URL: https://issues.apache.org/jira/browse/OOZIE-2949
> Project: Oozie
> Issue Type: Bug
> Reporter: Peter Cseh
> Assignee: Artem Ervits
>
> The current behavior of the Sqoop action is:
> {noformat}
> The Sqoop command can be specified either using the command element or
> multiple arg elements.
> When using the command element, Oozie will split the command on every space
> into multiple arguments.
> When using the arg elements, Oozie will pass each argument value as an
> argument to Sqoop.
> {noformat}
> This prevents the user to simply copy-paste the command worked in the shell
> into the workflow.xml.
> We should split the <command> field by taking quotes into account, similar to
> what OOZIE-2391
> did for the Spark action's <spark-opts> field.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
