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

Artem Ervits edited comment on OOZIE-2949 at 7/10/17 9:19 PM:
--------------------------------------------------------------

for reference, if I uncomment the singlequotes test I get the following

<code>
Failed tests:   
testSqoopActionWithArgsAndFreeFormQueryInSingleQuotes(org.apache.oozie.action.hadoop.TestSqoopActionExecutor):
 expected:<[SUCCEED]ED> but was:<[FAILED/KILL]ED>
<code>


was (Author: dbist13):
for reference, if I uncomment the singlequotes test I get the following

<noformat>
Failed tests:   
testSqoopActionWithArgsAndFreeFormQueryInSingleQuotes(org.apache.oozie.action.hadoop.TestSqoopActionExecutor):
 expected:<[SUCCEED]ED> but was:<[FAILED/KILL]ED>
<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
>    Affects Versions: 4.3.0
>            Reporter: Peter Cseh
>            Assignee: Artem Ervits
>             Fix For: 5.0.0
>
>         Attachments: OOZIE-2949-0.patch
>
>
> 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)

Reply via email to