typesense / typesense/typesense
Use field mapping to simplify field names for reducing storage volume?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.6k
- Forks
- 973
- Avg merge
- 18h 45m
- Merged PRs (30d)
- 4
Description
Is there a strategy of renaming field keys?
By mapping originally lengthy field keys (such as product_name, product_id, product_url) to shorter identifiers (e.g., a, b, c) during storage, which will reduce data storage overhead.
When reading data, restore the simplified identifiers to their original field names according to the mapping relationship.
Great always start from small details.
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
The issue does not name files, tests, or an entry point. First clarify whether field-key remapping is expected for all stored documents and how mappings would persist across reads; done would require an agreed design and validation of storage savings without changing returned field names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100