Evaluate need for index on content app's auto-distribute queries
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: @gerrod3 (gerrod)
Redmine Issue: 8777, https://pulp.plan.io/issues/8777
Content app is now going to auto-distribute the latest publication it can find for a distribution's repository. https://github.com/pulp/pulpcore/pull/1328/ This feature requires a query for the latest repository version sorted by earliest pulp_created date. This query could potentially need an index in the future to remain performant.
Parent issue: https://pulp.plan.io/issues/8760
References for a multi-column index: https://devcenter.heroku.com/articles/postgresql-indexes#multi-column-indexes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the content app's auto-distribute query described in the issue and the related pulpcore pull request 1328. Check how the latest repository version is selected and consult the PostgreSQL multi-column index reference. Done means determining whether an index is needed and recording or implementing a justified outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100