Bug 144 - Command Running
Summary: Command Running
Status: ASSIGNED
Alias: None
Product: Varia
Classification: Unclassified
Component: Flow (show other bugs)
Version: unspecified
Hardware: PC Linux
: P1 normal
Assignee: Werner Van Belle
URL:
Depends on:
Blocks: 142 96 139
  Show dependency tree
 
Reported: 2007-11-02 23:43 CET by Werner Van Belle
Modified: 2007-11-05 13:49 CET (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Werner Van Belle 2007-11-02 23:43:29 CET
 
Comment 1 Werner Van Belle 2007-11-05 12:37:28 CET
Running a command consists of passing along the filenames that go into the command. These filenames must be present in the inputs directory.
Comment 2 Werner Van Belle 2007-11-05 13:29:57 CET
To run a command we need to instantiate it, initialize the inputs, execute it and gather the results.
- instantiation is no problem
- to run it we need to place the input into the command isntance, which might be somewhat more tricky than expected.
- when the execution finished we need to inform the instantiator that the results are ready to be picked up at a specific place. This means that the caller should retrieve the full result directory in its own place.
Comment 3 Werner Van Belle 2007-11-05 13:49:32 CET
The command runner should wait for the command the finish.
The next question is then of course how we can pass things into the command. We have sql statements on one end, tables at the other, the next logical step, is to pass such data into a command.