quickwit-oss / quickwit-oss/quickwit
Better message when parsing doc mapper generates an error
Open
Nobody has claimed this yet.
backlog
enhancement
low-priority
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
I got this message:
Failed to parse command arguments: Timestamp field must be a fast field, please add fast property to your field timestamp`.``
Which is great but we need to add a context so that we know it's coming from the doc mapper.
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 doc mapper code that produces the reported "Failed to parse command arguments" message and the associated parsing tests, if present. Confirm how the error is surfaced and update the wording so it identifies the doc mapper context, then run the relevant parser tests or reproduce the timestamp fast-field error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100