in-memory
Here are 231 public repositories matching this topic...
-
Updated
Aug 1, 2021 - Go
In scope of #5970 Tarantool profile is introduced in lua-Harness suite. LuaJIT-related parts of the CI need to be adjusted for this profile usage.
Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.
This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients
-
Updated
Sep 29, 2021 - TypeScript
-
Updated
Jul 29, 2020 - Elixir
-
Updated
Sep 23, 2021 - Java
-
Updated
Dec 23, 2020 - C
-
Updated
Sep 28, 2021 - Java
-
Updated
Sep 20, 2021 - JavaScript
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
Apr 6, 2021 - C
-
Updated
Aug 15, 2021 - C++
Use of the $geoNear pipeline stage results in:
[Error 40324] Unrecognized pipeline stage name: '$geoNear'
It's clear it is not currently supported in de.bwaldvogel.mongo.backend.aggregation.Aggregation.java
Example Mongo query usage:
db.places.aggregate([
{
$geoNear: {
near: { type: "Point", coordinates: [ -73.99279 , 40.719296 ] },
distance
-
Updated
Sep 8, 2021 - C++
-
Updated
Jan 15, 2021 - Elixir
Tracking issue
-
Updated
Sep 14, 2021 - Rust
Go version: 1.17
Hazelcast Go Client version: 1.0.0
Hazelcast server version: 4.x
Number of the clients:
Cluster size, i.e. the number of Hazelcast cluster members:
OS version : Linux
Expected behaviour
logger.Config has method SetLogger that allows to set a custom logger matching Logger interface
Actual behaviour
logger.Config struct has no way to specify a custom logger im
-
Updated
Sep 4, 2021 - C++
-
Updated
Aug 20, 2021 - Go
-
Updated
Sep 30, 2021 - C++
Improve this page
Add a description, image, and links to the in-memory topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the in-memory topic, visit your repo's landing page and select "manage topics."
There is no technical difficulty to support
includeValueoption, looks like we are just missing it on the API level.See SO question