[jira] [Commented] (OOZIE-2949) Escape quotes whitespaces in Sqoop field

["Artem Ervits (JIRA)" <ji...@apache.org>]

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

Artem Ervits commented on OOZIE-2949:
-------------------------------------

[~gezapeti] can you provide a sqoop import command to reproduce the issue? Are you saying the following should handle double quotes?

{code}
import  --connect jdbc:hsqldb:file:db.hsqldb --table TT --target-dir hdfs://localhost:8020/user/tucu/foo -m 1
{code}

with a fix this should work too

{code}
import  --connect "jdbc:hsqldb:file:db.hsqldb" --table "TT" --target-dir "hdfs://localhost:8020/user/tucu/foo" -m "1"
{code}

do I understand the problem correctly?

> 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)