vectordotdev / vectordotdev/vector
New `warp10` sink
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
Warp10 is an open source time series database which is based on kafka & hbase. It comes with a powerful query langague WarpScript (a stack-oriented programming: https://www.warp10.io/content/03_Documentation/04_WarpScript/01_Concepts).
Here is how to push to Warp10 using HTTP: https://www.warp10.io/content/03_Documentation/03_Interacting_with_Warp_10/03_Ingesting_data/01_Ingress;
Here is the (GeoTimeSeries) GTS format required to push to Warp10: https://www.warp10.io/content/03_Documentation/03_Interacting_with_Warp_10/03_Ingesting_data/02_GTS_input_format.
Here is a crate to use to push: https://crates.io/crates/warp10.
More info here: https://www.warp10.io/.
Maybe I'll contribute if I get time to, but in any case I'll take time to answer any question.
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
No repository files, tests, or entry points are named. Start by reviewing existing sink implementations and the linked Warp10 HTTP and GTS documentation; done means Vector can send events to Warp10 in the required GTS format using the referenced Rust crate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100