quickwit-oss / quickwit-oss/quickwit
index update from UI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
the ui contains a few tabs related to index configuration (doc mapping, indexing settings, search settings, retention settings), which are read-only text editors. We could turn them into read-write editors, and add a "apply" button that causes the current values to be sent as an index update
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 UI tabs for doc mapping, indexing settings, search settings, and retention settings, then trace how their current values are loaded. Determine how an index update is submitted and how the Apply action should report success or failure. Done means all four editors accept changes and Apply sends the current values as an index update.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100