quickwit-oss/quickwit

Define and implement the user XP when searching for phrase query where position are not available.

Open

#1,363 opened on May 4, 2022

View on GitHubContributor guide
 (2 comments) (0 reactions) (1 assignee)Rust (580 forks)github user discovery
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (11,532 stars)
PR merge metrics
 (Avg merge 5d 18h) (41 merged PRs in 30d)

Description

When position are not available if the user search for a phrase query, we just return an error message explaining that phrase query are not supported for this field.

Still, users who haven't any position may still want a mechanism to feed tantivy with a phrase, and have it tokenized. (just not have position matching)

We need some syntax to do this.

  • backticks? text:`elu par cette crapule`
  • parenthesis? text:(elu par cette crapule)
  • bracket? text:[elu par cette crapule]
  • single quotation mark? text:'elu par cette crapule'

I have a preference for parenthesis or single quote.

Contributor guide

Research direction
Analyze the existing query syntax in tantivy and quickwit. Explore how to introduce a new syntax for phrase queries when positions are unavailable. Consider the preference for parentheses or single quotes and implement tokenization without position matching.
Tech stack
rust
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40