parse-community / parse-community/parse-server
Indexing owningId and releatedId in mongo _Join documents
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
Indexes are not automatically added when _Join: documents are created
Feature / Enhancement Description
By adding index for owningId and relatedId the query performance of mongo should improve. @davimacedo @mtrezza Now unless I am mistaken and it should not be required, let me know?

Example Use Case
Alternatives / Workarounds
Manually adding indexes
3rd Party References
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
Start by locating the MongoDB code that creates _Join documents and the existing index-creation path. Trace how owningId and relatedId are queried, then inspect the relevant database tests or add coverage if none exists. Done means the required indexes are created automatically and the behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mongodb
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100