Store (threading) message IDs as hashes only
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Is your feature request related to a problem? Please describe.
Message IDs can be long, like ~1kB. They take up a lot of space in the database.
Describe the solution you'd like
For threading, message IDs are only used for full comparison. We can normalize them with a simple hash function to 32B, for example, and shorten the DB column. The threading algorithm would still work.
Migration is heavy as we need to rewrite existing data.
Describe alternatives you've considered
No response
Additional context
- Related: #12862
- Earlier failed approach: https://github.com/nextcloud/mail/pull/10178
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 reviewing related issue #12862 and the earlier failed PR #10178, then locate where message IDs are stored and compared for threading and where database migrations are defined. Done means selecting a collision-safe normalization approach, shortening the column, and providing a migration for existing data without breaking threading.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100