quickwit-oss / quickwit-oss/quickwit
Document input format for data sources
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Currently options are as follows:
#[derive(Clone, Copy, Debug, Default, Eq, PartialEq, Serialize, Deserialize, utoipa::ToSchema)]
#[serde(rename_all = "snake_case")]
pub enum SourceInputFormat {
#[default]
Json,
OtlpLogsJson,
#[serde(alias = "otlp_logs_proto")]
OtlpLogsProtobuf,
#[serde(alias = "otlp_trace_json")]
OtlpTracesJson,
#[serde(
alias = "otlp_trace_proto",
alias = "otlp_trace_protobuf",
alias = "otlp_traces_proto"
)]
OtlpTracesProtobuf,
#[serde(alias = "plain")]
PlainText,
}
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 from the SourceInputFormat enum shown in the issue and review its variants, serde names, and aliases. Document the accepted input formats for data sources, including JSON, OTLP logs and traces, protobuf, and plain text; done means users can identify the supported names and aliases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100