quickwit-oss / quickwit-oss/quickwit
[Discussion] Json field usage in UI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
The JsonField enables Quickwit to be schemaless. While being a huge pro of the indexing experience, it will harden the search XP as the user will not know the available keys.
One solution would be to store keys in a dedicated field so that we could retrieve them in the UI.
Being able to make an aggregation on keys would be very nice too.
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 understanding how Quickwit's JsonField is represented and how the UI currently exposes searchable fields. Define whether the goal is to discover available keys, aggregate on keys, or both, then identify the indexing and UI work needed and establish tests or a demonstrable UI result as the completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- frontend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100