HSE 2.0 is now available

[hse-root]

We are excited to announce the release of HSE 2.0. This release represents a significant change to how HSE applications are deployed and managed. With HSE 2.0, we hope to address much of the feedback we have received from the user community.

Summary of Changes

HSE now runs entirely in user space on common Linux file systems. Specifically, the mpool kernel module is no longer required. This means that HSE 2.0 storage is not backward compatible with HSE 1.x.

Configuration and logging mechanisms now conform to best practices for containerized and cloud-native applications. This makes it easier to develop HSE applications that can run anywhere.

Transaction and cursor semantics now closely align with those found in other databases and storage engines. This makes it easier to port applications written for other storage engines to HSE.

We made syntactic changes to the native C API making it easier to both maintain backward compatibility going forward and develop alternate language bindings. This means that HSE 2.0 APIs are not backward compatible with HSE 1.x, though porting to HSE 2.0 is straight-forward.

Python language bindings are available for the HSE 2.0 API. We now use these for much of our test infrastructure, making is easier and faster to develop test cases.

In addition to these user-visible changes, we also redesigned the HSE data ingest pipeline to make it simpler, easier to maintain, more flexible, and better suited for future work that we are planning.

Call to Action

• Read the documentation to understand how HSE has changed.
• Migrate your HSE 1.x applications to HSE 2.0. While HSE 1.x is not going away immediately, it is no longer actively developed or maintained.
• Provide feedback on how HSE can better support your storage applications.

Cheers,
HSE Project Team