Actions
Task #3924
closed
Add a migration for the "vendor" field
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
2.18.0
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
Sprint 42
Quarter:
Description
In this previous issue [0], support was added for parsing the "vendor" field on RPM metadata, so that it could be used with search.
This will not affect RPM metadata already in the database, only new RPMs, so in order to get consistent results when searching by the vendor field, we need a migration to update this.
[0] https://pulp.plan.io/issues/2781
It is possible that this migration will take a long time to run. This migration should be tested with a large dataset to determine if it would be better to run it outside our normal migration workflow.
Related issues
Updated by dalley over 6 years ago
- Related to Issue #2781: Vendor field is present in db if RPM is uploaded, it is missed in case of sync added
Updated by daviddavis over 6 years ago
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
Updated by dalley about 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dalley
Updated by dalley about 6 years ago
- Status changed from ASSIGNED to POST
Added by dalley about 6 years ago
Updated by dalley about 6 years ago
- Platform Release changed from 2.17.1 to master
Updated by dalley about 6 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset 458efe58bc771d072dd4827cc6b9c1a5fe3015cf.
Updated by dkliban@redhat.com about 6 years ago
- Platform Release changed from master to 2.18.0
Updated by ttereshc almost 6 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Actions
.
Add a migration for the "vendor" field
closes #3924 https://pulp.plan.io/issues/3924