quickwit-oss / quickwit-oss/quickwit
Text fields without indexing / Ignoring fields
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
indexed: false is available for all types, except for text fields.
With mode mode: dynamic, the whole document is indexed. When you want to remove certain fields from search, you can't do that with text fields..
Defining the type could also be optional when a type is not indexed and not a fast field. (convert the json value to string in that case)
name: some_numer_or_maybe_text
stored: true
indexed: false
In tantivy it's possible to not index text fields by not setting index options:
https://docs.rs/tantivy/latest/src/tantivy/schema/field_type.rs.html#152-163
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 with the linked Tantivy source, src/tantivy/schema/field_type.rs, to understand how unindexed text fields are represented, then trace the corresponding Quickwit schema and indexing entry points. The issue names no Quickwit file or test; done should cover text fields with indexed: false and the proposed omitted-type behavior.
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
- 35/100