quickwit-oss / quickwit-oss/quickwit
Better logic for input format in queries
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Date and bytes field have different formats.
Currently one can configure
- a sorted list of input formats (format in the json ingested)
- the output format (format in the JSON output)
Then we have hardcorded the list of input formats we accept on the query side.
It would be better to build the list of input formats we accept on the query side based on the configure input formats and output format.
Following the idea that users will copy things for what they see, I think we should do the outputformat concatenated (with dedup) to the input format
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 query-side handling for date and bytes input formats and tracing how configured input formats and the output format are exposed. Verify the accepted query formats are derived from those settings, concatenated with duplicates removed, and add or update tests covering overlapping formats and both field types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100