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

Robert Kanter updated OOZIE-2377:
---------------------------------
    Description: 
OOZIE-2355 had the Hive2 action propagate all {{oozie.\*}} properties, other 
than {{oozie.launcher.*}} properties, to beeline.  We should also skip 
{{oozie.hive2.\*}} properties as well.  We've also seen some problems with this 
because of OOZIE-2332 where {{oozie.hive2.query}} has newlines, which 
{{beeline}} doesn't always like.  Given that the {{oozie.hive2.\*}} properties 
are meant for the launcher job anyway, we should just skip them.

We saw this issue on our internal unit test runs.

  was:OOZIE-2355 had the Hive2 action propagate all {{oozie.\*}} properties, 
other than {{oozie.launcher.*}} properties, to beeline.  We should also skip 
{{oozie.hive2.\*}} properties as well.  We've also seen some problems with this 
because of OOZIE-2332 where {{oozie.hive2.query}} has newlines, which 
{{beeline}} doesn't always like.  Given that the {{oozie.hive2.\*}} properties 
are meant for the launcher job anyway, we should just skip them.


> Hive2 Action should not propagate oozie.hive2.* properties to Beeline
> ---------------------------------------------------------------------
>
>                 Key: OOZIE-2377
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2377
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>             Fix For: trunk
>
>
> OOZIE-2355 had the Hive2 action propagate all {{oozie.\*}} properties, other 
> than {{oozie.launcher.*}} properties, to beeline.  We should also skip 
> {{oozie.hive2.\*}} properties as well.  We've also seen some problems with 
> this because of OOZIE-2332 where {{oozie.hive2.query}} has newlines, which 
> {{beeline}} doesn't always like.  Given that the {{oozie.hive2.\*}} 
> properties are meant for the launcher job anyway, we should just skip them.
> We saw this issue on our internal unit test runs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to