[jira] [Comment Edited] (OODT-585) How to disable envReplacement (either env or metadata-based) on pgeConfig customMetadata

["Andrew Hart (JIRA)" <ji...@apache.org>]

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

Andrew Hart edited comment on OODT-585 at 3/31/13 5:55 PM:
-----------------------------------------------------------

To build on what Chris described in the issue description, envReplacement is still desirable, the issue is that explicitly requesting that it be turned off, such as in the following example: 

{code:xml}
<customMetadata>
  <metadata key="Array" val="[2,3,4]" envReplace="false"/>
  ..
</customMetadata>
{code}

... currently appears to have no effect.
                
      was (Author: ahart):
    To build on what Chris described in the issue description, envReplacement is still desirable, the issue is that explicitly requesting that it be turned off, such as in the following example: 

{code}
<customMetadata>
  <metadata key="Array" val="[2,3,4]" envReplace="false"/>
  ..
</customMetadata>
{/code}

... currently appears to have no effect.
                  
> How to disable envReplacement (either env or metadata-based) on pgeConfig customMetadata
> ----------------------------------------------------------------------------------------
>
>                 Key: OODT-585
>                 URL: https://issues.apache.org/jira/browse/OODT-585
>             Project: OODT
>          Issue Type: Question
>          Components: pge wrapper framework
>            Reporter: Chris A. Mattmann
>            Assignee: Brian Foster
>            Priority: Critical
>             Fix For: 0.6
>
>
> [~bfoster] is it possible for envReplacement to be disabled in CAS-PGE customMetadata (both actual environment variables, as well as met-based replacement).
> Concrete use case:
> Say the following exists:
> {code:xml}
> <customMetadata>
>   <metadata key="Array" val="[2,3,4]"/>
> ..
> </customMetadata>
> {code}
> Is it possible to cause CAS-PGE to *not* replace the [2,3,4]. [~ahart] and [~riverma] had this question while working on the ASO mission. I suggested to them the following options:
> # Trying to encode the metadata as static task config in tasks.xml in the WM, and then reading it in CAS-PGE config. [apparently this didn't work]
> # Trying to use HTML entities for '[' and ']' [this didn't work either]
> # Write a CAS-PGE http://svn.apache.org/repos/asf/oodt/trunk/pge/src/main/java/org/apache/oodt/cas/pge/writers/DynamicConfigFileWriter.java that custom generated the input IDL script. [I still think this would work, but instead they wrote a sed script, and then used a replace char '<' and '>' in the met key to work around]
> Thoughts?

--
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