Official Java binding for TidesDB

5 stars 2 forks 5 watchers Java Mozilla Public License 2.0
database key-value-store library lsmtree storage-engine transactional
11 Open Issues Need Help Last updated: Aug 4, 2026

Open Issues Need Help

View All on GitHub
good first issue help wanted

Official Java binding for TidesDB

Java
#database#key-value-store#library#lsmtree#storage-engine#transactional
enhancement good first issue help wanted

Official Java binding for TidesDB

Java
#database#key-value-store#library#lsmtree#storage-engine#transactional
good first issue help wanted

Official Java binding for TidesDB

Java
#database#key-value-store#library#lsmtree#storage-engine#transactional
enhancement good first issue help wanted

Official Java binding for TidesDB

Java
#database#key-value-store#library#lsmtree#storage-engine#transactional

AI Summary: This issue requests the integration of a new purge API introduced in TidesDB v8.7.0. This API provides functionality to clear in-memory queues and buffers within the database. The task involves utilizing the `purge-database` and `purge-column-family` C API functions as referenced in the TidesDB documentation.

Complexity: 2/5
enhancement good first issue help wanted

Official Java binding for TidesDB

Java
#database#key-value-store#library#lsmtree#storage-engine#transactional

AI Summary: The issue proposes adding a new database-level configuration option named `max_memory_usage`. This option, of type `size_t`, will be integrated into the `tidesdb_config_t` structure.

Complexity: 2/5
good first issue help wanted

Official Java binding for TidesDB

Java
#database#key-value-store#library#lsmtree#storage-engine#transactional
enhancement good first issue help wanted

Official Java binding for TidesDB

Java
#database#key-value-store#library#lsmtree#storage-engine#transactional
enhancement good first issue help wanted

Official Java binding for TidesDB

Java
#database#key-value-store#library#lsmtree#storage-engine#transactional

AI Summary: This issue requests the addition of a new API to clone an existing column family within the TidesDB database. The cloning operation should create a complete, independent copy of all keys, values, and metadata, ensuring atomicity and data consistency. This feature is intended for use cases like creating snapshots, backups, or isolated testing environments.

Complexity: 4/5
good first issue help wanted

Official Java binding for TidesDB

Java
#database#key-value-store#library#lsmtree#storage-engine#transactional
enhancement good first issue help wanted

Official Java binding for TidesDB

Java
#database#key-value-store#library#lsmtree#storage-engine#transactional
enhancement good first issue

Official Java binding for TidesDB

Java
#database#key-value-store#library#lsmtree#storage-engine#transactional