Task #3871
closed
Task model has PK that is not consistent with the rest of the data model.
100%
Description
The Task.id is still a UUID. Consistency in a relational schema is important. We should add a Task.job_id (uuid) to correlate with rq/redis.
https://github.com/pulp/pulp/blob/master/pulpcore/pulpcore/app/models/task.py#L269
Updated by daviddavis over 6 years ago
- Tracker changed from Issue to Task
- Sprint/Milestone set to 3.0.0
- % Done set to 0
Updated by jortel@redhat.com about 6 years ago
- Status changed from NEW to ASSIGNED
Updated by daviddavis almost 6 years ago
- Assignee changed from CodeHeeler to daviddavis
Should I expose job_id in the REST API? On the one hand, it shouldn't be something users need or ought to know but on the other, it might help to debug.
Updated by bmbouter almost 6 years ago
+1 to exposing it. They may want to correlate it with a RQ monitoring system they setup separately.
Updated by jortel@redhat.com almost 6 years ago
bmbouter wrote:
+1 to exposing it. They may want to correlate it with a RQ monitoring system they setup separately.
+1 for same ^^ reasons.
Updated by daviddavis almost 6 years ago
- Status changed from ASSIGNED to POST
Added by daviddavis almost 6 years ago
Added by daviddavis almost 6 years ago
Revision 06445689 | View on GitHub
Create a new Task field job_id to store rq job ids
Updated by daviddavis almost 6 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|06445689cddeaa7509721dfe34beb48ecac7cc42.
Updated by bmbouter almost 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Create a new Task field job_id to store rq job ids
fixes #3871 https://pulp.plan.io/issues/3871