Issue #7851
closed
don't generate sqlite db files for yum metadata if pulp2 exporter didn't use generate them
Description
sqlite files are slow to generate and at migration time they are being created even if they weren't generated for the source repository.
Related issues
Updated by dalley about 4 years ago
- Related to Issue #7842: 'table db_info already exists' on consecutive migrations added
Updated by dalley about 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dalley
Updated by dalley almost 4 years ago
- Status changed from ASSIGNED to POST
Added by dalley almost 4 years ago
Added by dalley almost 4 years ago
Revision 6665089c | View on GitHub
Don't generate sqlite metadata unless Pulp 2 config says so
pulp_rpm provides a toggle for generating sqlite metadata, defaulting to off, added in #7852. If the Pulp 2 config does specify generation of sqlite metadata, then we need to re-enable it.
Added by dalley almost 4 years ago
Revision 6665089c | View on GitHub
Don't generate sqlite metadata unless Pulp 2 config says so
pulp_rpm provides a toggle for generating sqlite metadata, defaulting to off, added in #7852. If the Pulp 2 config does specify generation of sqlite metadata, then we need to re-enable it.
Updated by dalley almost 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp:pulp-2to3-migration|6665089c27351eb7126cb1cfdb52db9388902e92.
Updated by ttereshc almost 4 years ago
- Sprint/Milestone changed from 0.9.0 to 0.7.0
Updated by pulpbot almost 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Don't generate sqlite metadata unless Pulp 2 config says so
pulp_rpm provides a toggle for generating sqlite metadata, defaulting to off, added in #7852. If the Pulp 2 config does specify generation of sqlite metadata, then we need to re-enable it.
closes: #7851 https://pulp.plan.io/issues/7851