airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raminderjeet Singh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-994) Craft Airavata Execution Management API
Date Wed, 29 Jan 2014 16:24:17 GMT

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

Raminderjeet Singh commented on AIRAVATA-994:
---------------------------------------------

The structure looks simple and good to me. I have suggestions in EXPERIMENT_CONFIGURATION_DATA
table, We need to have separate table for WORKFLOW_INPUT_KEY and WORKFLOW_INPUT_VAL as it
can be more than one values. We should call these fields EXPERIMENT_INPUT_KEY and VALUE. Similarly
we need to have table to record output values. 

> Craft Airavata Execution Management API 
> ----------------------------------------
>
>                 Key: AIRAVATA-994
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-994
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Airavata API
>            Reporter: Suresh Marru
>             Fix For: 1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message