[
https://issues.apache.org/jira/browse/OOZIE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Salamon updated OOZIE-2949:
----------------------------------
Comment: was deleted
(was: We could create a hack solution like:
# Extending {{ExpressionEvaluatorImpl}} and not using the cache
# Counting EL expression evaluations and drop {{ExpressionEvaluatorImpl}} and
start over after a while
The best solution (just like [~gezapeti] suggested) is to replace commons el.
I've checked our code, it seems to be this is the only place we use
{{commons.el}} in Oozie. There are seveal EL evaluators listed here:
[https://stackoverflow.com/a/17051440/21348] We might check JEXL (
[http://commons.apache.org/proper/commons-jexl/] ) since we already use that
in other parts of Oozie.
)
> 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: Andras Salamon
> Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-2949-0.patch, OOZIE-2949-01.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
(v7.6.3#76005)
