[Search processor] Support static index mapping
Open
Nobody has claimed this yet.
enhancement
replication
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 82
- Avg merge
- 18h 22m
- Merged PRs (30d)
- 51
Description
Add support for static index mapping instead of dynamic. This could be handled:
- By manually creating a new index and adding an alias with the new mapping
- Automatically creating a new index when a schema change happens with the new static mapping, and pointing to the same alias, with the option to reindex to make sure all data from the previous index is ported over to the new one.
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 search processor and its current dynamic index-mapping and alias behavior. Define whether manual creation or automatic schema-change handling is required, including alias replacement and optional reindexing, then validate the chosen flow across schema changes and existing data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, go
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100