Opened 15 years ago
Closed 15 years ago
#1378 closed enhancement (fixed)
Base1PluginExecuter should link the result directory with the transformation
| Reported by: | Jari Häkkinen | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | major | Milestone: | BASE 2.15 |
| Component: | coreplugins | Version: | |
| Keywords: | Cc: |
Description
Related to ticket:1279
When a BASE1 plug-in stores result files the files are placed in a sub-directory in the file tree like
.../PluginName/JobId
PluginName cannot be removed since there may be several result directories but JobId is related to the transformation and can be removed (as is done for the content in JobId as of the fixed ticket:1279).
Change History (6)
follow-up: 2 comment:1 by , 15 years ago
comment:2 by , 15 years ago
Replying to nicklas:
This is not really related to #1279. The directory in question is not linked in any way to the job or to the transformation that created it. It is just a directory that happens to have a name that matches the id of a job. To get the automatic removal as described in #1279 is simply solved by having the Base1PluginExecuter add a link to the directory. But then maybe the other files (stdin.txt, stdout.txt, etc...) should not be linked since it may be kind of strange to have both the directory and the files within it linked?
Would this affect the display of the transformation generated files (section Items related to this transformation) in the analysis tree such that not all files in the result directory will be linked but rather only the result directory?
comment:3 by , 15 years ago
| Milestone: | → BASE 2.15 |
|---|---|
| Summary: | Deleting transformations created by Base1PluginExecuter leaves result root directory → Base1PluginExecuter should link the result directory with the transformation |
Yes... only the directory would be visible which would make the Items related to this transformation section rather useless. It is probably better to keep links to both the directory and the files.
comment:4 by , 15 years ago
| Component: | web → coreplugins |
|---|
comment:5 by , 15 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:6 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
This is not really related to #1279. The directory in question is not linked in any way to the job or to the transformation that created it. It is just a directory that happens to have a name that matches the id of a job. To get the automatic removal as described in #1279 is simply solved by having the Base1PluginExecuter add a link to the directory. But then maybe the other files (stdin.txt, stdout.txt, etc...) should not be linked since it may be kind of strange to have both the directory and the files within it linked?