Uploaded image for project: 'OODT'
  1. OODT
  2. OODT-585

How to disable envReplacement (either env or metadata-based) on pgeConfig customMetadata

    XMLWordPrintableJSON

    Details

    • Type: Question
    • Status: Resolved
    • Priority: Critical
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 1.1
    • Component/s: pge wrapper framework
    • Labels:
      None

      Description

      Brian Foster 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:

      <customMetadata>
        <metadata key="Array" val="[2,3,4]"/>
      ..
      </customMetadata>
      

      Is it possible to cause CAS-PGE to not replace the [2,3,4]. Andrew Hart and Rishi Verma had this question while working on the ASO mission. I suggested to them the following options:

      1. 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]
      2. Trying to use HTML entities for '[' and ']' [this didn't work either]
      3. 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?

        Attachments

          Activity

            People

            • Assignee:
              bfoster Brian Foster
              Reporter:
              chrismattmann Chris A. Mattmann
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: