key-value-store
Here are 380 public repositories matching this topic...
-
Updated
Apr 27, 2022 - C#
-
Updated
Nov 6, 2021 - Java
-
Updated
Feb 26, 2022 - JavaScript
-
Updated
Apr 24, 2022 - Go
-
Updated
Apr 27, 2022 - C++
-
Updated
Feb 20, 2022 - Python
-
Updated
Jan 31, 2022 - Go
-
Updated
Apr 27, 2022 - Java
-
Updated
Aug 27, 2021 - Go
-
Updated
Apr 26, 2022 - Rust
-
Updated
Apr 27, 2022 - C
-
Updated
Dec 14, 2021 - Java
-
Updated
Dec 23, 2020 - C
-
Updated
Apr 19, 2022 - Go
Right now, PebblesDB uses a lot of memory for the TableCache (caching metadata) and for the bloom filters used for each sstable.
We want to add a command line option for PebblesDB which would limit the total amount of memory used by PebblesDB for the TableCache and bloom filters.
When using the specified amount of memory, preference should be given first to the table cache, and then bloom
-
Updated
Feb 13, 2022 - Elixir
-
Updated
Apr 26, 2022 - Shell
-
Updated
Mar 8, 2022 - Clojure
Transactional API can be configured with custom backoff strategies. We should support it for raw API as well.
There are no external core dependencies other than LZ4 and Snappy which are not used unless compression is configured. So they should be installable.
libraryDependencies += "io.swaydb" %% "lz4" % "version"
//OR
libraryDependencies += "io.swaydb" %% "snappy" % "version"For now we have to exclude
-
Updated
Mar 6, 2022 - Rust
-
Updated
Apr 26, 2022 - C
-
Updated
Jan 26, 2022 - Rust
-
Updated
Nov 18, 2019
-
Updated
Sep 22, 2020 - Go
It would be better and easier to debug a program if the BytesEncoding and BytesDecoding traits could return any error type.
To do so we need to modify the Error enum and more specifically the Encoding and Decoding variants to wrap a Box<dyn Error>.
Improve this page
Add a description, image, and links to the key-value-store topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the key-value-store topic, visit your repo's landing page and select "manage topics."
Our CMake build process produces tarball packages using the cpack
TGZtarget. This produces a server and client package with a file layout meant to match where the various artifacts go.Meanwhile, the packages we include on the download page are a flat archive of various binaries produced by the build process. This include one regular package and one debug package with debug symbols for a few