[
https://issues.apache.org/jira/browse/OODT-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-585.
------------------------------------
Resolution: Won't Fix
can be worked around with tasks.xml config per task with envReplace turned off
> 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: 1.1
>
>
> [~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 was sent by Atlassian JIRA
(v6.4.14#64029)
