Add h5i-db to Databases > Timeseries - #329
Open
Koukyosyumei wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds h5i-db to the bottom of the Databases > Timeseries category.
What it is: an embedded, versioned time series database written in Rust, with a Python package and a CLI. It stores Parquet and queries it through DataFusion SQL, adding time series operators on top: ASOF join, timezone aware time bucketing, gapfill and resample, rolling windows.
Why it fits: the existing Timeseries entries are all server or cluster systems. h5i-db covers the in-process end of the same category, the way DuckDB does for general analytics: one directory, no server, no daemon. What is distinct is that storage is immutable and versioned, so every write is an atomic commit, any past version reads in constant time, and a bad ingest is one restore away from undone. Reads can also be pinned to a decision time, which bounds a query to data that had actually arrived by that instant.
Apache-2.0, published on crates.io and PyPI, documented at https://db.h5i.dev/manual/ with usage examples in the README.
Single suggestion, added to the bottom of the relevant category, no emojis or images in the entry. Disclosure: I am the author.