Hiperspace 2.4.0
Prefix ReservedSee the version list below for details.
dotnet add package Hiperspace --version 2.4.0
NuGet\Install-Package Hiperspace -Version 2.4.0
<PackageReference Include="Hiperspace" Version="2.4.0" />
<PackageVersion Include="Hiperspace" Version="2.4.0" />
<PackageReference Include="Hiperspace" />
paket add Hiperspace --version 2.4.0
#r "nuget: Hiperspace, 2.4.0"
#:package Hiperspace@2.4.0
#addin nuget:?package=Hiperspace&version=2.4.0
#tool nuget:?package=Hiperspace&version=2.4.0
Hiperspace
Hiperspace is an Object technology that uses a key-addressable store to expand an application data-model beyond the limits of memory that can be directly referenced in main memory.
Elements are not duplicated or changing to match database shapes.
Elements are serialized directly using Protocol Buffers
to and from key/value structure for storage in memory stores including CXL
expanded and pooled memory, shared cache , local SSD or key-value durable databases.
Elements that are not currently being used are released from main memory, and transparently (and quickly) reloaded when referenced. Memory stores allows petabytes of data to be addressed.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 is compatible. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net8.0
- Microsoft.Bcl.HashCode (>= 6.0.0)
- protobuf-net.Core (>= 3.2.52)
- System.Numerics.Tensors (>= 9.0.5)
-
net9.0
- Microsoft.Bcl.HashCode (>= 6.0.0)
- protobuf-net.Core (>= 3.2.52)
- System.Numerics.Tensors (>= 9.0.5)
NuGet packages (3)
Showing the top 3 NuGet packages that depend on Hiperspace:
Package | Downloads |
---|---|
Hiperspace.Heap
Hiperspace heap store for session, edge and testing purposes |
|
Hiperspace.Rocks
HiperSpace RocksDB adaptor |
|
Hiperspace.SQL
# Hiperspace.SQL Hiperspace.SQL is a full SQL query engine for Hiperspace, supporting the full range of joins, aggregations, and subqueries. Hiperspace.SQL provides the same query functionality as a .NET client can use with LINQ queries, but without the need to write code in C#/F# Hiperspace fully supports point-in-time "time travel" queries that are not possible with Python Data-Frames or DuckDB ## Features - Hiperspace.SQL is not limited to queries of columns within a table, but supports the full navigation of properties of Hiperspace elements - Where a column is a complex object it is returned as a JSON object - Executing a batch of SQL statements return columnar data frames (dictionary of column-name and array of values) - Explain SQL returns the execution plan, detailing the SetSPaces accessed and keys used for search (Key, Index, Scan) - The Parquet method returns a Parquet file that can be used with any Apache Parquet library, or added to DuckDB OLAP store |
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last Updated |
---|---|---|
2.4.6 | 219 | 9/23/2025 |
2.4.4 | 271 | 8/7/2025 |
2.4.2 | 164 | 7/28/2025 |
2.4.0 | 217 | 7/10/2025 |
2.3.8 | 207 | 7/1/2025 |
2.3.7 | 205 | 6/18/2025 |
2.3.3 | 212 | 6/5/2025 |
2.2.2 | 228 | 5/5/2025 |
2.2.1 | 294 | 4/14/2025 |
2.2.0 | 161 | 3/29/2025 |
2.1.3 | 302 | 3/5/2025 |
2.1.1 | 192 | 2/15/2025 |
2.1.0 | 170 | 1/24/2025 |
2.0.0 | 147 | 1/14/2025 |
1.3.9 | 187 | 11/15/2024 |
1.3.3 | 162 | 11/1/2024 |
1.3.1 | 228 | 10/18/2024 |
1.3.0 | 219 | 10/5/2024 |
1.2.31 | 227 | 9/15/2024 |
1.2.26 | 197 | 9/1/2024 |
1.2.18 | 150 | 8/6/2024 |
1.2.12 | 143 | 7/26/2024 |
1.2.9 | 188 | 7/19/2024 |
1.2.8 | 195 | 7/15/2024 |
1.2.4 | 223 | 7/4/2024 |
1.2.0 | 229 | 5/30/2024 |
1.0.46 | 151 | 5/11/2024 |
1.0.40 | 176 | 4/22/2024 |
1.0.34 | 235 | 3/14/2024 |
1.0.28 | 251 | 2/26/2024 |
1.0.27 | 214 | 2/16/2024 |
1.0.24 | 271 | 1/11/2024 |
1.0.23 | 264 | 1/1/2024 |
1.0.1 | 241 | 11/18/2023 |
## Overview
**Hiperspace** is uses [protobuf](https://protobuf.dev/) wire-format to serialise **elements** in the domain **SubSpace**
for peristence is a *key/value* *(primarilly [RocksDB](https://rocksdb.org/))* with *minimal* transformation, and no padding.
The schema can evolve without the need to alter an historically, using two rules:
* #id numeric aliases for {entities, segments, aspects, keys, values, indexes} are never reused
* The datatype of {keys, values} are never changed (*other than by renaming items*)
### MetaModel
The `MetaModel` contains a list of all the *Element* types stored within a Hiperspace and the data types of each *key*
and *value*. The `MetaModel` is eternal - additional *Element* are added as tyhe schema changes, but never removed, to ensure that
older build can still read the data that they understand.
When a **Hiperspace** is opened, the domain `MetaModel` is compared with the `MetaModel` stored in the **Hiperspace** to ensure the
above rules have not been compromised. All read and write after open uses the wire-format directly without transformation from store
through to client application (including browser web-assembly).
### MetaMap
To support range access, the bytes in wire-format for keys are reordered to place message lengths at the end of the `byte[]`
for each key. This is especially important for *segments* (*where the parent knows only the `owner` part of the key, and *indexes*).
The `MetaMap` is an ordered array of #id and mapping of *key/value* #id to the element #id of references. The `MetaMap` is coded
in the domain assembly. This release adds the capability to remove key references without the need to crerate a new element type, by
regenerating the `MetaMap` from the `MetaModel` stored in **Hiperspace**.
### Change
This release changes the method signatures {`KeyPath`, `IndexPath`} to support a MetaMap built at load-time, and
adds additional abstract methods to the `Hiperspace` to load and merge `MetaModel`.
The `MetaModelException` exception type has been added to provide detailed diagnostics, if the `MetaModel` is not compatible.