Bug #3831
[Crunch] inconsistent find_or_create behavior in pipeline runner vs job
Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Story points:
0.5
Description
The pipeline runner automatically adds a find_or_create = true field for jobs in the pipeline, if one does not exist. This inverts the documented default behavior at the job level (which is find_or_create = false).
Either we need to change the pipeline runner behavior, or we need to explicitly document this. It's very confusing to have a different default at different layers in our stack, though.
History
#1
Updated by Ward Vandewege over 7 years ago
- Description updated (diff)
#2
Updated by Ward Vandewege over 7 years ago
- Subject changed from [Crunch] inconsistent find_or_create behavior in pipeline runner vs jobs to [Crunch] inconsistent find_or_create behavior in pipeline runner vs job
#3
Updated by Ward Vandewege over 7 years ago
- Target version set to Arvados Future Sprints
#4
Updated by Tom Clegg over 7 years ago
- Status changed from New to In Progress
- Story points set to 0.5
#5
Updated by Tom Clegg about 5 years ago
- Status changed from In Progress to Closed
#6
Updated by Tom Clegg about 5 years ago
- Target version deleted (
Arvados Future Sprints)