Mark Grover created OOZIE-2241:
----------------------------------
Summary: Oozie tries to resolve ${CONDITIONS} when it should be
directly passed to Sqoop
Key: OOZIE-2241
URL: https://issues.apache.org/jira/browse/OOZIE-2241
Project: Oozie
Issue Type: Bug
Components: action
Affects Versions: 4.2
Reporter: Mark Grover
When using the Sqoop action, one may have a legitimate need to pass a query
down to Sqoop. In particular, sqoop has special meaning for a variable
${CONDITIONS} which can be a part of the query being passed to Sqoop. However,
Oozie, understandably but mistakenly so tries to resolve ${CONDITIONS} as any
other variable and fails to do so.
An example of what I just described is at
https://gist.github.com/markgrover/cf62e475f15e3d6612ce#file-gistfile1-txt-L17
The sqoop command works fine when used on command line without oozie but not
with oozie.
Another thing to note is I'd be satisfied with an end result where escaping
${CONDITIONS} would make use pass it straight through to Sqoop but I couldn't
figure out what to use to escape either. I tried the following 3 and none of
them worked:
1. \${CONDITIONS}
2. $${CONDITIONS}
3. Enclosing the entire value of <command> field in single quotes
Thanks in advance!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
