Question on timing with API, running workflows, and setting metadata
I'd like to have an external program that registers a file by absolute path (link, not upload) in a data library, then immediately starts a workflow on it. My question is to whether or not that will work in the general case where: - The system is configured to set metadata externally - The compute grid is busy (so the set_meta call is queued for some time) In this case, will the workflow be queued and set idle, waiting for the set_meta() to complete? Or will the API call to register the data library block until the set_meta() is done? Thanks! John Duddy Sr. Staff Software Engineer Illumina, Inc. 9885 Towne Centre Drive San Diego, CA 92121 Tel: 858-736-3584 E-mail: jduddy@illumina.com<mailto:jduddy@illumina.com>
This should not lock. The job(s) for the workflow will be queued until they're able to execute, but the call will return. -Dannon On Aug 2, 2011, at 4:17 PM, Duddy, John wrote:
I’d like to have an external program that registers a file by absolute path (link, not upload) in a data library, then immediately starts a workflow on it. My question is to whether or not that will work in the general case where: - The system is configured to set metadata externally - The compute grid is busy (so the set_meta call is queued for some time)
In this case, will the workflow be queued and set idle, waiting for the set_meta() to complete? Or will the API call to register the data library block until the set_meta() is done?
Thanks!
John Duddy Sr. Staff Software Engineer Illumina, Inc. 9885 Towne Centre Drive San Diego, CA 92121 Tel: 858-736-3584 E-mail: jduddy@illumina.com
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
participants (2)
-
Dannon Baker -
Duddy, John