liquidvotingio / liquidvotingio/api
Review composite indexing
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 17
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Review the performance impacts of composite indexing.
Including:
1. whether multiple less complex indices are required when more complex indices already include the indexed fields
2. whether we can improve the ordering off fields in complex indices
Resulting from a discussion on #227
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
No files, tests, or entry points are named in the issue. Start by reviewing the database index definitions and discussion in issue #227; done means assessing redundant indices and field ordering, then documenting or implementing the resulting decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100