[
https://issues.apache.org/jira/browse/OODT-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-930.
------------------------------------
Resolution: Won't Fix
I wanted to file this issue and record the work around. It's not hard, but I
ran into this with BigTranslate. Say you want to create a new key, MyKey, which
is not present in the incoming static metadata or in dynamic metadata, but that
you want e.g., to be the value of the already present in static, dynamic or pge
metadata, JobId. What you can do is declare:
<metadata key="MyKey" val="[JobId]" worklowMet="true"/>
This will create a new key, MyKey, and populate it with the value of JobId, and
then push it to the workflow metadata. This gets around the problem and isn't
too hard to deal with.
> Valueless key with workflowMet tag should push into workflow met with
> existing value and not look for key-ref
> -------------------------------------------------------------------------------------------------------------
>
> Key: OODT-930
> URL: https://issues.apache.org/jira/browse/OODT-930
> Project: OODT
> Issue Type: Improvement
> Components: pge wrapper framework
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 1.1
>
>
> Currently in CAS-PGE if you declare a valueless key in pgeMetadata CAS-PGE
> XML builder tries to look for a key-ref, and if not present it will throw an
> exception about having a key with a null value. It would be nice if CAS-PGE
> looked into the incoming static or dynamic met and tried to resolve the value
> based on those.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
