[ 
https://issues.apache.org/jira/browse/OOZIE-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Kanter updated OOZIE-1353:
---------------------------------

    Attachment: OOZIE-1353.patch

It turns out that there's some behavior of the -X thing that isn't (clearly) 
documented that if you have a -D argument after the -X, then it goes into the 
<configuration>

e.g. (oozie hive ... -X -Dfoo=bar) results in the job having
{code:xml}
<configuration>
   <property>
      <name>foo</name>
      <value>bar</value>
   </property>
</configuration>
{code}

So, to accommodate that behavior and to maintain backwards compatibility, I 
didn't actually remove the -X from the hive command; instead, all non -D 
arguments after -X are ignored for hive (they still work for pig).

I added the ability to specify parameters for the scripts for both pig and hive 
by doing {{-Pkey1=value1 -Pkey2=value2}} etc.  This is important because 
previously you couldn't specify these for hive and its a lot easier to do this 
on the CLI than have a file in HDFS for pig to do this.

The -X values were sent as {{oozie.hive.options.1}} etc, so I made the 
parameters similar: {{oozie.hive.script.params.1}} etc.  

I also did some minor refactoring/cleanup.  

I tested submitting pig and hive workflows from the CLI with various arguments 
and updated the tests.


I'll add docs for hive and clarify the pig ones in OOZIE-1352.  I'll then fix 
the REST API docs in OOZIE-1183
                
> hive CLI should not allow -X command
> ------------------------------------
>
>                 Key: OOZIE-1353
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1353
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Bowen Zhang
>            Assignee: Robert Kanter
>         Attachments: OOZIE-1353.patch
>
>
> Hive CLI -X command currently results in an xml schema error which means 
> oozie is generating schema error. We need to disable this for people to use.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to