quickwit-oss / quickwit-oss/quickwit
Backward compatibilty tests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
We could consider to extend the python tests for compatibly tests between quickwit versions. We already have the notion of engine to differentiate between quickwit and elasticsearch.
https://github.com/quickwit-oss/quickwit/tree/main/quickwit/rest-api-tests
For that we would need to extend the script to:
- Install multiple Quickwit versions (
engine)- cargo install from commit hash?
- We can't install it as e.g.
quickwit_oldcurrently https://github.com/rust-lang/cargo/issues/12366) - Maybe just copy the compiled binary to
quickwit_old
- We can't install it as e.g.
- Download from a precompiled place ?
- cargo install from commit hash?
- Add a mechanism to execute different queries for each engine
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 in quickwit/rest-api-tests and read the existing Python test script's handling of the engine setting. Work out how multiple Quickwit versions can be installed or copied and how queries can differ by engine. Done means the compatibility suite runs against multiple Quickwit versions and supports engine-specific queries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100