quickwit-oss / quickwit-oss/quickwit

Support for relaxed search schema in ES compatible endpoint to support direct query from OpenSearch Dashboards

Open
#5,097 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Is your feature request related to a problem? Please describe.

As of now Quickwit ES compatible endpoint is extremely strict on schema and do not allow optional fields passed to the query by OS Dashboards.

Describe the solution you'd like

Quickwit shouldn't reject queries with optional fields and should ignore them instead.

Describe alternatives you've considered

So far proxy resolve that, but solution is ugly.

Additional context

Examples of OSD queries here

Errors list:

  • .version unknown field version, expected one of ...
  • .script_fields unknown field script_fields, expected one of ...
  • .docvalue_fields unknown field docvalue_fields, expected one of ...
  • ._source unknown field _source, expected one of ...
  • .highlight unknown field highlight, expected one o
  • .query.bool.filter[].range.<>.format OneOrMany could not deserialize any variant:\n One: invalid type: sequence, expected string or map\n Many: unknown field format, expected one of gt, gte, lt, lte, boost
  • .aggs.2.date_histogram.calendar_interval tantivy error: An invalid argument was passed: 'calendar_interval parameter "1m" in date histogram is unsupported, only fixed_interval is supported'

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.

Research direction

Start at the ES-compatible endpoint handling the OpenSearch Dashboards queries and compare its validation behavior with the linked proxy and example requests. Define the supported optional fields and confirm that unsupported optional fields are ignored without changing valid query results, including the listed range and date-histogram cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch, rust
Domain
api, backend, search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.