Issue #7851
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
Associated revisions
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.
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.
History
#1
Updated by dalley 8 months ago
- Related to Issue #7842: 'table db_info already exists' on consecutive migrations added
#3
Updated by ipanova@redhat.com 7 months ago
- Sprint set to Sprint 87
#8
Updated by dalley 6 months ago
- Status changed from POST to MODIFIED
Applied in changeset pulp:pulp-2to3-migration|6665089c27351eb7126cb1cfdb52db9388902e92.
Please register to edit this issue
.
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