Contributing

Interested in learning how sybil works or making sybil better?

Ways to contribute

You can contribute by reporting bugs and opening issues, adding new features (or feature requests), reporting performance numbers or even adding your use cases and example datasets

Feature Ideas

Below are some self-contained / stand-alone features that would improve sybil. If any seem interesting, pick them up and make a pull request. if you need any help or direction, open an issue and I'd be glad to talk about them

• add late materialization (or early filtering) to queries
• add snappy (or other in memory) string compression for string columns
• turn ingestion log into b-tree based append log that's robust & faster
• improve storage for high cardinality strings on disk
• add go-charts (or other) image output for time series queries
• add float column type
• add microbenchmarks
• better histogram approximation methods, like WARP (a fast KDE method) or trapezoidal estimation or HDR Histograms
• add datetime column type (that can be read in as either integers or string based) and datetime ops like HOUR, DAY, MONTH that are fast to calculate
• add ability to write query specs in JSON instead of using CLI args
• stand-alone ARIMA / Bayesian time series alerting server
• add process memory limits and fine grained memory controls

Finished

• add re-usable memory slabs for loading blocks off disk, so when one block is no longer in use it can be used again without a re-alloc
• add standalone weco alerting server