quickwit-oss / quickwit-oss/quickwit

Clarify default text options // add a string type

Open
#156 1 comment 0 reactions 1 assignee View on GitHub

@fmassot is already working on this.

Since Mar 29, 2022.

bug enhancement
Dominant language
Rust
Stars
11.7k
Forks
597
Avg merge
2d 22h
Merged PRs (30d)
37

Description

Need to check the following points:

  • can we index with freq and positions in quickwit?
  • what are the tokenizer available and how to add new ones?

Adding a "string" field type could be convenient for several reasons:

  • very simple default configuration: want full text search => text field, if you only want to store some strings like email, id => string field
  • Elastic use also two types, "text" and "keyword"

On cons is that the two data types store a string, so we're just adding a type to simplify configuration.

One more thing, if we want to add such a type, it's better to do it now.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.