quickwit-oss / quickwit-oss/quickwit

more efficient way to map input documents to what we index and store

Open
#4,166 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement low-priority
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.
we currently allow document mapping with VRL. It's very flexible, it's great, but sadly it leaves a lot of performance on the table

Describe the solution you'd like
having some other way to remap document that may be harder to setup, or less flexible, but faster. For instance we could support using wasm to do the remapping.

Describe alternatives you've considered
let people embed their own rust code to remap by themselves. It requires recompiling, and being somewhat familiar with quickwit source code, and maintaining patches, so it's not really great for most people.

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

The issue names no files, tests, or entry points. Start by locating the existing VRL document-mapping path and measuring its performance, then compare the proposed WASM and embedded-Rust alternatives. The issue needs an agreed design, scope, and performance target before completion can be defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, wasm
Domain
search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.