Closed Cenxn closed 2 months ago
I just realised workflow can also has "requirements" filed. Should we separate the model or how do you think? @Cenxn
yes, @anisahn09 we will probably have to add requirements and hints json fields to job as well.
yes, @anisahn09 we will probably have to add requirements and hints json fields to job as well.
I see, is there also "hints" for task?
yes, @anisahn09 we will probably have to add requirements and hints json fields to job as well.
Also if there will be two requirement tables, maybe we should name them in the same way. Like Requirement_Task and Requirement_Job, or something like that. How do you think? @Cenxn @waleedev01
yes, @anisahn09 we will probably have to add requirements and hints json fields to job as well.
Also if there will be two requirement tables, maybe we should name them in the same way. Like Requirement_Task and Requirement_Job, or something like that. How do you think? @Cenxn @waleedev01
I guess we are using the requirements json field, so we don't need to manage this table name issue.
yes, @anisahn09 we will probably have to add requirements and hints json fields to job as well.
Also if there will be two requirement tables, maybe we should name them in the same way. Like Requirement_Task and Requirement_Job, or something like that. How do you think? @Cenxn @waleedev01
I guess we are using the requirements json field, so we don't need to manage this table name issue.
Wait so there will be only one Requirement
table? or two table, one for task, one for job?
yes, @anisahn09 we will probably have to add requirements and hints json fields to job as well.
Also if there will be two requirement tables, maybe we should name them in the same way. Like Requirement_Task and Requirement_Job, or something like that. How do you think? @Cenxn @waleedev01
I guess we are using the requirements json field, so we don't need to manage this table name issue.
Wait so there will be only one
Requirement
table? or two table, one for task, one for job?
Requirements will be a json payload field in both tasks and Job, not a table.
Since CWLSchemaValidator automatically verifies that the file conforms to the cwl syntax and the required data types, storing it as a JSON payload shouldn't cause serious problems in type constraint.