[
https://issues.apache.org/jira/browse/OODT-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229972#comment-13229972
]
[email protected] commented on OODT-411:
----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4359/
-----------------------------------------------------------
(Updated 2012-03-15 08:08:37.402954)
Review request for oodt, Chris Mattmann, Ricky Nguyen, Paul Ramirez, and Thomas
Bennett.
Changes
-------
Since required only a small change, added support for isVector() to
PgeTaskMetKeys which allows workflow static metadata to be split on comma if it
is a multi-value type (but still allowing scalar values to contain commas
without getting split into multi-values)
Summary
-------
Will allow for specification of new keys while still supported legacy keys
This addresses bug OODT-411.
https://issues.apache.org/jira/browse/OODT-411
Diffs (updated)
-----
trunk/pge/src/main/java/org/apache/oodt/cas/pge/PGETaskInstance.java 1300799
trunk/pge/src/main/java/org/apache/oodt/cas/pge/config/XmlFilePgeConfigBuilder.java
1300799
trunk/pge/src/main/java/org/apache/oodt/cas/pge/metadata/PcsMetadataKeys.java
1300798
trunk/pge/src/main/java/org/apache/oodt/cas/pge/metadata/PgeTaskMetKeys.java
1300799
trunk/pge/src/test/org/apache/oodt/cas/pge/metadata/TestPgeTaskMetKeys.java
1300799
Diff: https://reviews.apache.org/r/4359/diff
Testing
-------
existing unit-tests for PgeTaskMetKeys
Thanks,
brian
> Port CAS-PGE's PcsMetadataKeys to PgeTaskMetKeys
> ------------------------------------------------
>
> Key: OODT-411
> URL: https://issues.apache.org/jira/browse/OODT-411
> Project: OODT
> Issue Type: Sub-task
> Components: pge wrapper framework
> Affects Versions: 0.3
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.4
>
> Attachments: OODT-411.2012-03-14.patch.txt
>
>
> Will allow for specification of new keys while still supported legacy keys
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira