quickwit-oss / quickwit-oss/quickwit
consider using a non-versionned index for otel
Open
Nobody has claimed this yet.
enhancement
otel
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
we currently use index with versions in their names. With index updates, we could just update indexes instead of creating new ones. In doing so, we must make sure we don't clobber indexes with a configuration different than our default.
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 by tracing how versioned OTEL indexes are created and updated, then determine how index configuration is compared with the default. Done means updates reuse a non-versioned index without clobbering an index whose configuration differs from the default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100