quickwit-oss / quickwit-oss/quickwit
Small improvements on the ES field cap endpoint
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
- if one of the index patterns doesn’t match anything, we should return a 200: we should call
check_all_index_metadata_foundmethod in the root function (as it's done for a classic search endpoint - return undocumented
typevalue - /_field_caps URL
Query Parameters
- fields
- allow_no_indices (ignored)
- expand_wildcards (ignored)
- accept
ignore_unavailablequery parameter and ignore it silently -
include_unmappedparameter -
typesparameter -
filtersparameter
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 ES field cap endpoint and reviewing how the checked query parameters are handled, especially the documented behavior for unmatched index patterns and the type value. Then trace the remaining include_unmapped, types, and filters parameters and verify that the endpoint accepts them with the intended field-cap response behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, rust
- Domain
- api, search
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100