airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-3211) Assign wildcard matches to OutputDataObjectType instead of creating new ones
Date Tue, 17 Sep 2019 16:40:00 GMT

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

ASF subversion and git services commented on AIRAVATA-3211:
-----------------------------------------------------------

Commit 80157e5674983537c56db41e6dbcf9e0af140a1b in airavata's branch refs/heads/staging from
Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata.git;h=80157e5 ]

AIRAVATA-3211 Wildcard matches update output values


> Assign wildcard matches to OutputDataObjectType instead of creating new ones
> ----------------------------------------------------------------------------
>
>                 Key: AIRAVATA-3211
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3211
>             Project: Airavata
>          Issue Type: Bug
>          Components: helix implementation
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>
> Currently the OutputDataStagingTask handles wildcard matches by adding additional OutputDataObjectTypes
to the Experiment model. The problem with this is that this breaks the association between
the name of the original OutputDataObjectType and these newly created ones. The output view
providers (AIRAVATA-3029) functionality in the Django portal uses this association to be able
to register custom output view providers as metadata of the OutputDataObjectType in the Application
Interface and have those applied to experiments that completed before the custom output view
provider was registered (the experiments will have a copy of the OutputDataObjectType metadata
for their outputs, but won't get any updates to metadata so portal code looks at the original
Application Interface to see if there are any other output view providers registered).
> Instead I propose:
> * if the output type is URI, then take the first wildcard match, create DataProduct and
set the data product URI as the value of the output. This will overwrite the wildcard pattern
in the value field, but that should be okay since the wildcard pattern is no longer needed.
> * if the output type is a URI_COLLECTION, then create DataProducts for all matching files
and set the value to a comma delimited string out data product URIs.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message