You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:49:10 UTC

[jira] [Commented] (OOZIE-206) GH-254: XConfiguration should give precedence to variables over sys-props in ${} expressions

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

Hadoop QA commented on OOZIE-206:
---------------------------------

tucu00 remarked:
This help with usability and will fix an issue with the examples where ${user.name} is used in job.properties but it is wrongfully interpreted:

oozie.wf.application.path=hdfs://localhost:9000/user/${user.name}/examples/apps/no-op

> GH-254: XConfiguration should give precedence to variables over sys-props in ${} expressions
> --------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-206
>                 URL: https://issues.apache.org/jira/browse/OOZIE-206
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> Currently if a config file as a property
>   user.name=foo
>   foo.output=/user/${user.name}/output
> If *XConfiguration* is used from a process owned by the user 'oozie' then *foo.output* gets resolved to */user/oozie/output*
> For how Oozie uses Configurations it should resolve to */user/foo/output*
> I'll raise an issue in Hadoop to change this, but I'm fearing that they'll claim that a change to current behavior will break existing applications.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira